Tigase XMPP Server Board

Tigase server development: RE: Tigase 5.1.0 support of RFC 6120

Mon, 03/16/2015 - 16:17

Hi Artur,

I see that the newest releases of Tigase have implemented RFC 6120. So was wanting to know if 5.1.0 also implemented 6120. There are times when we need to quickly determine if a certain functionality is supported so it is helpful to know which RFC is officially supported.

Thanks!

Categories: Tigase Forums

Tigase server development: RE: Tigase 5.1.0 support of RFC 6120

Mon, 03/16/2015 - 16:05

Differences between RFC-6120 and RFC-3920 were very minimal and for sure Tigase is/was compatible with the older RFC. All new versions should be also compatible with the more recent RFC, however, we always try to preserve backward compatibility and not change behavior from one version to another in default setup. Maybe you could specify what exactly you have in mind I would be able to help you better.
Do you have any specific RFC section or requirement in mind?

Categories: Tigase Forums

Tigase server development: RE: Disable AMP component

Mon, 03/16/2015 - 15:50

You might want to enable Message plugin instead of AMP to process messages. Otherwise Messages can be handled by a default handler which may route them a bit differently from the spec.

Categories: Tigase Forums

Tigase server development: Tigase 5.1.0 support of RFC 6120

Mon, 03/16/2015 - 10:42

Just a quick question. Did version 5.1.0 support RFC 6120?

Thank you.

Categories: Tigase Forums

Tigase server development: RE: Disable AMP component

Mon, 03/16/2015 - 04:24

Thanks Wojciech.

Categories: Tigase Forums

Tigase server development: RE: Disable AMP component

Mon, 03/16/2015 - 04:23

No, AMP is not used internally and can be safely disabled.

Categories: Tigase Forums

Tigase server development: RE: about jaxmpp2 registration

Mon, 03/16/2015 - 04:21

您发给我的信件已经收到。

--------------------------------------------
网易163邮箱--中文邮箱第一品牌,2280兆超大空间,支持超大附件,全国唯一24小时客户服务。
欢迎您来注册使用。网易邮件中心:http://mail.163.com

This is an automatic reply, confirming that your e-mail was received.Thank you 邮箱使用小提示 想让对方更及时看到你的邮件,可以试试发到""。 无需事先开通,还有短信提醒。了解网易手机邮箱详情
Categories: Tigase Forums

Tigase server development: RE: about jaxmpp2 registration

Mon, 03/16/2015 - 04:05

您发给我的信件已经收到。

--------------------------------------------
网易163邮箱--中文邮箱第一品牌,2280兆超大空间,支持超大附件,全国唯一24小时客户服务。
欢迎您来注册使用。网易邮件中心:http://mail.163.com

This is an automatic reply, confirming that your e-mail was received.Thank you 邮箱使用小提示 想让对方更及时看到你的邮件,可以试试发到""。 无需事先开通,还有短信提醒。了解网易手机邮箱详情
Categories: Tigase Forums

Tigase server development: Disable AMP component

Mon, 03/16/2015 - 03:57

I disabled AMP component and plugin because I don't need AMP.

message-router/components/msg-receivers/amp.active[B]=false --sm-plugins=-amp

Are there any counterindications for disabling AMP? Is it used internally somehow to process messages? Assuming of course that my clients don't use AMP features.

Thanks

Categories: Tigase Forums

Tigase server development: RE: File transfer in Tigase

Mon, 03/16/2015 - 03:48

From the server perspective handling Jingle is only about forwarding stanzas (IQs) without special support and it works. When you receive service unavailable it's mostly caused by the recipient side not supporting jingle.

Categories: Tigase Forums

Tigase server development: RE: about jaxmpp2 registration

Mon, 03/16/2015 - 03:48

您发给我的信件已经收到。

--------------------------------------------
网易163邮箱--中文邮箱第一品牌,2280兆超大空间,支持超大附件,全国唯一24小时客户服务。
欢迎您来注册使用。网易邮件中心:http://mail.163.com

This is an automatic reply, confirming that your e-mail was received.Thank you 邮箱使用小提示 想让对方更及时看到你的邮件,可以试试发到""。 无需事先开通,还有短信提醒。了解网易手机邮箱详情
Categories: Tigase Forums

Tigase server development: RE: about jaxmpp2 registration

Mon, 03/16/2015 - 03:47

As the error suggests:
Can't establish encrypted connection javax.net.ssl.SSLHandshakeException: Cerificate hostname doesn't match domain name you want to connect.

certificate you're using on the server is wrong and causes connection to drop - i.e. CN name in the certificate name doesn't match SessionObject.DOMAIN_NAME, "im.test.com"

Categories: Tigase Forums

Tigase server development: RE: Tigase closes a session after met inactive time.

Mon, 03/16/2015 - 03:44

You could set inactivity time to higher level, but I'd say that better option would be to simply implement client-side logic to reconnect if the session expires.

Categories: Tigase Forums

Tigase server development: File transfer in Tigase

Sun, 03/15/2015 - 05:03

Does tigase support file transfer thru jingle? I am using smack library to transfer a file and the result of the command always returns service unavailable

Categories: Tigase Forums

Tigase server development: about jaxmpp2 registration

Sun, 03/15/2015 - 03:11

您发给我的信件已经收到。

--------------------------------------------
网易163邮箱--中文邮箱第一品牌,2280兆超大空间,支持超大附件,全国唯一24小时客户服务。
欢迎您来注册使用。网易邮件中心:http://mail.163.com

This is an automatic reply, confirming that your e-mail was received.Thank you 邮箱使用小提示 想让对方更及时看到你的邮件,可以试试发到""。 无需事先开通,还有短信提醒。了解网易手机邮箱详情
Categories: Tigase Forums

Tigase server development: about jaxmpp2 registration

Sun, 03/15/2015 - 02:55

The init file:
--virt-hosts = im.test.com
--auth-db-uri = jdbc:mysql://localhost:3306/tigasedb?user=root&password=root
--user-db-uri = jdbc:mysql://localhost:3306/tigasedb?user=root&password=root
#--sm-cluster-strategy-class = tigase.cluster.strategy.OnlineUsersCachingStrategy
--user-db = mysql
--admins =
--comp-name-6 = message-archive
--comp-name-5 = rest
--comp-name-4 = stun
--auth-db = tigase-auth
--comp-name-3 = proxy
config-type = --gen-config-def
--comp-name-2 = pubsub
--comp-name-1 = muc
--cluster-mode = true
--sm-plugins = +message-archive-xep-0136,+jabber:iq:auth,+urn:ietf:params:xml:ns:xmpp-sasl,+urn:ietf:params:xml:ns:xmpp-bind,+urn:ietf:params:xml:ns:xmpp-session,+jabber:iq:register,+jabber:iq:roster,+presence,+jabber:iq:privacy,+jabber:iq:version,+http://jabber.org/protocol/stats,+starttls,+msgoffline,+vcard-temp,+http://jabber.org/protocol/commands,+jabber:iq:private,+urn:xmpp:ping,+basic-filter,+domain-filter,+pep,-zlib
--debug = server,xmpp.impl,db,cluster,muc,component
#--comp-class-1 = tigase.muc.cluster.MUCComponentClustered
--comp-class-1 = tigase.muc.MUCComponent
muc/muc-lock-new-room[B]=false
--external = muc.im.test.com:muc-pass:connect:5270:devel.tigase.org:accept
--comp-class-2 = tigase.pubsub.cluster.PubSubComponentClustered
--comp-class-3 = tigase.socks5.Socks5ProxyComponent
--comp-class-4 = tigase.stun.StunComponent
--comp-class-5 = tigase.http.rest.RestMessageReceiver
--comp-class-6 = tigase.archive.MessageArchiveComponent
message-archive/archive-repo-uri=jdbc:mysql://localhost:3306/tigasedb?user=root&password=root&useUnicode=true&characterEncoding=UTF-8&autoCreateUser=true
sess-man/plugins-conf/message-archive-xep-0136/component-jid=
sess-man/plugins-conf/message-archive-xep-0136/auto=true
#sess-man/plugins-conf/message-archive-xep-0136/default-store-method=body
#sess-man/plugins-conf/message-archive-xep-0136/required-store-method=body

*******************************************************************************************************
my client code is :

public void registration(final String username,final String password,final String email) throws JaxmppException{

final Jaxmpp jaxmpp = new Jaxmpp();
jaxmpp.getProperties().setUserProperty(SessionObject.DOMAIN_NAME, "im.test.com"); jaxmpp.getModulesManager().register(new InBandRegistrationModule());
jaxmpp.getSessionObject().setProperty(InBandRegistrationModule.IN_BAND_REGISTRATION_MODE_KEY, Boolean.TRUE); jaxmpp.getEventBus().addHandler(
InBandRegistrationModule.ReceivedRequestedFieldsHandler.ReceivedRequestedFieldsEvent.class,
new InBandRegistrationModule.ReceivedRequestedFieldsHandler() { @Override
public void onReceivedRequestedFields(SessionObject sessionObject, IQ responseStanza) { try {
jaxmpp.getModule(InBandRegistrationModule.class).register(username, password, email,
new AsyncCallback() { @Override
public void onError(Stanza responseStanza, ErrorCondition error) throws JaxmppException {
System.out.println("Account registration error: " + error);
} @Override
public void onSuccess(Stanza responseStanza) throws JaxmppException {
System.out.println("registrationSuccess");
} @Override
public void onTimeout() throws JaxmppException {
System.out.println("Account registration failed.");
}
});
} catch (JaxmppException e) {
System.out.println(e);
} } });
jaxmpp.login(true);
}

The console is:

2015-3-15 17:46:50 tigase.jaxmpp.j2se.Jaxmpp createConnector
信息: Using SocketConnector
2015-3-15 17:46:50 tigase.jaxmpp.j2se.connectors.socket.SocketConnector createSessionLogic
信息: Using XEP-0077 mode!!!!
2015-3-15 17:46:50 tigase.jaxmpp.j2se.connectors.socket.SocketConnector start
信息: Resolving SRV recrd of domain 'im.test.com'
2015-3-15 17:46:50 tigase.jaxmpp.j2se.connectors.socket.SocketConnector start
信息: Opening connection to im.test.com/127.0.0.1:5222
2015-3-15 17:46:51 tigase.jaxmpp.j2se.connectors.socket.SocketConnector$3 handshakeCompleted
信息: TLS completed javax.net.ssl.HandshakeCompletedEvent[source=1e152c5[SSL_RSA_WITH_RC4_128_MD5: Socket[addr=im.test.com/127.0.0.1,port=5222,localport=59522]]]
2015-3-15 17:46:51 tigase.jaxmpp.j2se.connectors.socket.SocketConnector proceedTLS
严重: Can't establish encrypted connection
javax.net.ssl.SSLHandshakeException: Cerificate hostname doesn't match domain name you want to connect.
at tigase.jaxmpp.j2se.connectors.socket.SocketConnector.proceedTLS(SocketConnector.java:469)
at tigase.jaxmpp.j2se.connectors.socket.SocketConnector.onTLSStanza(SocketConnector.java:390)
at tigase.jaxmpp.j2se.connectors.socket.SocketConnector.processElement(SocketConnector.java:566)
at tigase.jaxmpp.j2se.connectors.socket.SocketConnector$5.processElement(SocketConnector.java:765)
at tigase.jaxmpp.j2se.connectors.socket.Worker$1.nextElement(Worker.java:49)
at tigase.jaxmpp.j2se.connectors.socket.XMPPDomBuilderHandler.endElement(XMPPDomBuilderHandler.java:152)
at tigase.xml.SimpleParser.parse(SimpleParser.java:323)
at tigase.jaxmpp.j2se.connectors.socket.Worker.run(Worker.java:101)

*******************************************************************************************************
The XMPP SERVER console is:

MR-OUT: from=null, to=null, DATA=<iq type="set" id="c2s--c2s3" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_OPENED"><x xmlns="jabber:x:data" type="submit"><field var="session-id"><value>01b24814-776b-4aa9-b0ae-62fe85dfb465</value></field><field var="hostname"><value>im.test.com</value></field><field var="xml:lang"><value>en</value></field></x></command></iq>, SIZE=436, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set
MR-IN: from=null, to=null, DATA=<iq type="set" id="c2s--c2s3" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_OPENED"><x xmlns="jabber:x:data" type="submit"><field var="session-id"><value>01b24814-776b-4aa9-b0ae-62fe85dfb465</value></field><field var="hostname"><value>im.test.com</value></field><field var="xml:lang"><value>en</value></field></x></command></iq>, SIZE=436, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set
MR-IN: from=null, to=null, DATA=<iq type="set" id="c2s--c2s3" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_OPENED"><x xmlns="jabber:x:data" type="submit"><field var="session-id"><value>01b24814-776b-4aa9-b0ae-62fe85dfb465</value></field><field var="hostname"><value>im.test.com</value></field><field var="xml:lang"><value>en</value></field></x></command></iq>, SIZE=436, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set
MR-OUT: from=sess-man@ja6e5njdvi8v4l0, to=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, DATA=<iq type="result" id="c2s--c2s3" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"/>, SIZE=122, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=result
MR-IN: from=sess-man@ja6e5njdvi8v4l0, to=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, DATA=<iq type="result" id="c2s--c2s3" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"/>, SIZE=122, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=result
MR-OUT: from=null, to=null, DATA=<iq type="get" id="d5f96556-223a-4b20-82e6-527ce5c7ecc6" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="GETFEATURES"/></iq>, SIZE=223, XMLNS=null, PRIORITY=HIGH, PERMISSION=NONE, TYPE=get
MR-IN: from=null, to=null, DATA=<iq type="get" id="d5f96556-223a-4b20-82e6-527ce5c7ecc6" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="GETFEATURES"/></iq>, SIZE=223, XMLNS=null, PRIORITY=HIGH, PERMISSION=NONE, TYPE=get
MR-IN: from=null, to=null, DATA=<iq type="get" id="d5f96556-223a-4b20-82e6-527ce5c7ecc6" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="GETFEATURES"/></iq>, SIZE=223, XMLNS=null, PRIORITY=HIGH, PERMISSION=NONE, TYPE=get
MR-OUT: from=sess-man@ja6e5njdvi8v4l0, to=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, DATA=<iq type="result" id="d5f96556-223a-4b20-82e6-527ce5c7ecc6" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"><command xmlns="http://jabber.org/protocol/commands" node="GETFEATURES"><ver xmlns="urn:xmpp:features:rosterver"/><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism></mechanisms><register xmlns="http://jabber.org/features/iq-register"/><auth xmlns="http://jabber.org/features/iq-auth"/></command></iq>, SIZE=562, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=result
MR-IN: from=sess-man@ja6e5njdvi8v4l0, to=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, DATA=<iq type="result" id="d5f96556-223a-4b20-82e6-527ce5c7ecc6" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"><command xmlns="http://jabber.org/protocol/commands" node="GETFEATURES"><ver xmlns="urn:xmpp:features:rosterver"/><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism></mechanisms><register xmlns="http://jabber.org/features/iq-register"/><auth xmlns="http://jabber.org/features/iq-auth"/></command></iq>, SIZE=562, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=result
MR-IN: from=sess-man@ja6e5njdvi8v4l0, to=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, DATA=<iq type="result" id="d5f96556-223a-4b20-82e6-527ce5c7ecc6" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"><command xmlns="http://jabber.org/protocol/commands" node="GETFEATURES"><ver xmlns="urn:xmpp:features:rosterver"/><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism></mechanisms><register xmlns="http://jabber.org/features/iq-register"/><auth xmlns="http://jabber.org/features/iq-auth"/></command></iq>, SIZE=562, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=result
MR-OUT: from=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, to=sess-man@ja6e5njdvi8v4l0, DATA=<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>, SIZE=51, XMLNS=urn:ietf:params:xml:ns:xmpp-tls, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null
MR-IN: from=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, to=sess-man@ja6e5njdvi8v4l0, DATA=<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>, SIZE=51, XMLNS=urn:ietf:params:xml:ns:xmpp-tls, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null
MR-IN: from=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, to=sess-man@ja6e5njdvi8v4l0, DATA=<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>, SIZE=51, XMLNS=urn:ietf:params:xml:ns:xmpp-tls, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null
MR-OUT: from=sess-man@ja6e5njdvi8v4l0, to=null, DATA=<iq type="set" id="tig1" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"><command xmlns="http://jabber.org/protocol/commands" node="STARTTLS"><x xmlns="jabber:x:data" type="submit"/><proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/></command></iq>, SIZE=287, XMLNS=null, PRIORITY=NORMAL, PERMISSION=LOCAL, TYPE=set
MR-IN: from=sess-man@ja6e5njdvi8v4l0, to=null, DATA=<iq type="set" id="tig1" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"><command xmlns="http://jabber.org/protocol/commands" node="STARTTLS"><x xmlns="jabber:x:data" type="submit"/><proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/></command></iq>, SIZE=287, XMLNS=null, PRIORITY=NORMAL, PERMISSION=LOCAL, TYPE=set
MR-IN: from=sess-man@ja6e5njdvi8v4l0, to=null, DATA=<iq type="set" id="tig1" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"><command xmlns="http://jabber.org/protocol/commands" node="STARTTLS"><x xmlns="jabber:x:data" type="submit"/><proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/></command></iq>, SIZE=287, XMLNS=null, PRIORITY=NORMAL, PERMISSION=LOCAL, TYPE=set
MR-OUT: from=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, to=sess-man@ja6e5njdvi8v4l0, DATA=<iq type="set" id="21060c8d-6e99-450f-a05c-fd46ea9fac3e" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"/></iq>, SIZE=225, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set
MR-IN: from=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, to=sess-man@ja6e5njdvi8v4l0, DATA=<iq type="set" id="21060c8d-6e99-450f-a05c-fd46ea9fac3e" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"/></iq>, SIZE=225, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set
MR-IN: from=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, to=sess-man@ja6e5njdvi8v4l0, DATA=<iq type="set" id="21060c8d-6e99-450f-a05c-fd46ea9fac3e" to="sess-man@ja6e5njdvi8v4l0" from="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"/></iq>, SIZE=225, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set
MR-OUT: from=sess-man@ja6e5njdvi8v4l0, to=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, DATA=<iq type="result" id="21060c8d-6e99-450f-a05c-fd46ea9fac3e" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"/>, SIZE=149, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=result
MR-IN: from=sess-man@ja6e5njdvi8v4l0, to=c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794, DATA=<iq type="result" id="21060c8d-6e99-450f-a05c-fd46ea9fac3e" to="c2s@ja6e5njdvi8v4l0/127.0.0.1_5222_127.0.0.1_49794" from="sess-man@ja6e5njdvi8v4l0"/>, SIZE=149, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=result

please help me to resolve,thanks.

Categories: Tigase Forums

Tigase server development: Tigase closes a session after met inactive time.

Sat, 03/14/2015 - 03:48

I am using Tigase 5.2.3. I have added a property for a bosh inactivity timer for 60sec. So that the BOSH session will be cleared after 60 sec if it is inactive(i.e, Internet problem in client side, Browser closed, system is in sleep mode and etc.). My web client don't an option to re-create a session if user is in logged in last session is closed. So I move on to the other idea called, Tigase should always keeps a session(Even inactivity time meets).

1) Is this option is available in Tigase?
2) And Is there any other way to handle this problem and how?

Your help will be appreciated.

Categories: Tigase Forums

Tigase server development: RE: Connection timeout when using WebSockets

Sat, 03/14/2015 - 03:17

Hi again

Thank you very much for your help - I much appreciate it.

Best regards
Claus Weng

Categories: Tigase Forums

Tigase server development: RE: Connection timeout when using WebSockets

Fri, 03/13/2015 - 11:54
There are quite a few XEPs for this, each covers a different communication level:
  1. Stream Management
  2. Advanced Message Processing
  3. Message Delivery Receipts

All of them are supported by Tigase software, on both the server and the client side.

Categories: Tigase Forums

Tigase server development: RE: Problem with Stream Management

Fri, 03/13/2015 - 05:09

Hi Andrzej,

I simulate connection failure connecting from a mobile device and then putting it on airplane mode, so the server will not be notified of anything from the device. This should replicate quite well the use case of a network failure, and it could be compared to the cable unplugged.

The watchdog tries to ping the device every X second as I told it, so that part is great, but before a disconnection to be detected it passes far more than the expected 5+ minutes - (almost 15 minutes)

After that, I get for every single message a 404 message recipient-unavailable as the one below

<error type="wait" code="404"><recipient-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error>

after which the message will be stored

2015-03-13 11:54:05.151 [in_0-amp] JDBCMsgRepository.storeMessage() FINEST:

Does this seem consistent to you ? My only aim is to have the storeMessage() called earlier, any suggestion ?

All the best,
Luca

Categories: Tigase Forums

Pages

Get in touch

We provide software products, consulting and custom development services

Tigase, Inc.
100 Pine Street, Suite 1250
San Francisco, CA 94111, USA
Phone: (415) 315 9771

Follow us on:

Twitter

Back to Top