Tigase XMPP Server Board

Tigase server administration: RE: Need Information regarding the Tigase XMPP Libraries that wheth...

Mon, 05/18/2015 - 05:03

Hi,

Thanks for the information.

Actually we are interesting in Tigase opensource Jar/library( like JSO provided) that Tigase library could support xmpp Streaming handshake (both DIALBACK, TLS + SASL) and PRESENCE , IM message parsing.

From our sample code, we open severSocket on 5269 port and then attach that socket to stream object of xmpp library(provided by your library).

Could you please help us in providing this information that whether Tigase provide any xmpp library for Server to Server communication/support?

And for FIPS specification,I have raised a question to my Manager , i will update you once got some information.

Regards,

Ravish Aggarwal

Categories: Tigase Forums

Tigase server administration: Please delete it

Mon, 05/18/2015 - 03:54

Delete it

Categories: Tigase Forums

Tigase server administration: RE: User hangs in memory

Mon, 05/18/2015 - 01:55

1) As shown in the attached log file, other users were able to connect to Tigase server and add-user or change-password scripts for them worked normally. Password for this users was changed in database as well, so db connection was successful.
2) There were no same NPE’s in tigase-console.log.

Categories: Tigase Forums

Tigase server development: how to slove Queue overflow and sessionmanager packet is to big

Mon, 05/18/2015 - 01:24

when tigase run a while,the tigase-monitor show the SM Traffic Total value is too big,is't up to 1329348,and queue is also big,upto 211071,The Warning:Overflow is also cameup, It seems that thereis something need process,and very slow

in the tigase.log.0,i found many log output as:

2015-05-11 16:05:48.062 [scheduler_pool-4-thread-1-c2s] ClientConnectionManager$StoppedHandler.timeOutExpired() INFO: No response within time limit received for a packet: from=c2s@localhost/122.225.11.237_5222_183.132.207.114_62313, to=sess-man@localhost, DATA=<iq id="348feaeb-5876-4887-9b3a-08f03029534a" type="set" to="sess-man@localhost" from="c2s@localhost/122.225.11.237_5222_183.132.207.114_62313"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"/></iq>, SIZE=224, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set
2015-05-11 16:05:48.069 [scheduler_pool-4-thread-1-c2s] ClientConnectionManager$StoppedHandler.timeOutExpired() INFO: No response within time limit received for a packet: from=c2s@localhost/122.225.11.237_5222_115.192.149.148_53044, to=sess-man@localhost, DATA=<iq id="3bed2197-44de-4f87-8946-d2093e222f55" type="set" to="sess-man@localhost" from="c2s@localhost/122.225.11.237_5222_115.192.149.148_53044"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"/></iq>, SIZE=224, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set

Thanks in advance.

Categories: Tigase Forums

Tigase server development: RE: Unordered messages with lost messages & duplication

Mon, 05/18/2015 - 00:58

Aejaz Muslim wrote:

Then I disable the network connection for A & B
sends messages, 1,2,3,4,5,6.

After connection is enabled for A, it receives
1,6,4,4,2,6(in this order).

From the attached server logs:
2015-05-15 07:27:43.453 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<success xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>, SIZE=51, XMLNS=urn:ietf:params:xml:ns:xmpp-sasl, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=null 2015-05-15 07:27:43.478 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1, Writing packet: from=null, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<stream:features><sm xmlns="urn:xmpp:sm:3"/><register xmlns="http://jabber.org/features/iq-register"/><ver xmlns="urn:xmpp:features:rosterver"/><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/><session xmlns="urn:ietf:params:xml:ns:xmpp-session"/></stream:features>, SIZE=315, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null 2015-05-15 07:27:43.569 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-4" to="asengar@dev1/47ce0cc2ec34487f"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"><jid>asengar@dev1/47ce0cc2ec34487f</jid></bind></iq>, SIZE=187, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:27:43.598 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-6" to="asengar@dev1/47ce0cc2ec34487f"/>, SIZE=89, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:27:43.668 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-8" to="asengar@dev1/47ce0cc2ec34487f"><query xmlns="jabber:iq:roster"/></iq>, SIZE=126, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:27:43.819 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<presence from="asengar@dev1/47ce0cc2ec34487f" xmlns="jabber:client" id="6NXL1-10" to="asengar@dev1"><c node="http://www.igniterealtime.org/projects/smack" xmlns="http://jabber.org/protocol/caps" hash="sha-1" ver="os2Kusj3WEOivn5n4iFr/ZEO8ls="/></presence>, SIZE=256, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=AUTH, TYPE=null 2015-05-15 07:27:43.822 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-13" to="asengar@dev1/47ce0cc2ec34487f"/>, SIZE=90, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:27:43.835 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<presence from="asengar@dev1/47ce0cc2ec34487f" xmlns="jabber:client" id="6NXL1-11" to="asengar@dev1"><c node="http://www.igniterealtime.org/projects/smack" xmlns="http://jabber.org/protocol/caps" hash="sha-1" ver="os2Kusj3WEOivn5n4iFr/ZEO8ls="/></presence>, SIZE=256, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=AUTH, TYPE=null 2015-05-15 07:28:21.993 [in_11-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_33881, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_33881 Socket[addr=/50.161.80.209,port=33881,localport=5222], jid: 852275@dev1/2101e057de2545e2, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_33881, DATA=<message from="asengar@dev1/47ce0cc2ec34487f" xmlns="jabber:client" id="6NXL1-17" type="chat" to="852275@dev1"><body>Dr. Ashvini Sengar:#@#:asengar:#@#:1:#@#:test</body></message>, SIZE=179, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:21.996 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="asengar@dev1/47ce0cc2ec34487f" xmlns="jabber:client" id="6NXL1-17" type="chat" to="852275@dev1"><body>Dr. Ashvini Sengar:#@#:asengar:#@#:1:#@#:test</body></message>, SIZE=179, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:28.203 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-19" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:test1</body></message>, SIZE=182, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:28.212 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-19" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:test1</body></message>, SIZE=182, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:39.925 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-20" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:1</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:39.928 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-20" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:1</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:41.867 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-21" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:2</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:41.884 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-21" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:2</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:48.044 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-22" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:3</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:48.052 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-22" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:3</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:51.008 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-23" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:4</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:51.019 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-23" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:4</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:53.928 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-24" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:5</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:53.938 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-24" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:5</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:56.729 [in_15-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, type: accept, Socket: c2s@dev1/216.218.236.91_5222_101.57.48.175_18092 Socket[addr=/101.57.48.175,port=18092,localport=5222], jid: 852275@dev1/3af3281fc19d25b9, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_101.57.48.175_18092, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-25" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:6</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:28:56.741 [in_10-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[addr=/50.161.80.209,port=34124,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-25" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:6</body></message>, SIZE=178, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:29:23.381 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<success xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>, SIZE=51, XMLNS=urn:ietf:params:xml:ns:xmpp-sasl, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=null 2015-05-15 07:29:23.403 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1, Writing packet: from=null, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<stream:features><sm xmlns="urn:xmpp:sm:3"/><register xmlns="http://jabber.org/features/iq-register"/><ver xmlns="urn:xmpp:features:rosterver"/><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/><session xmlns="urn:ietf:params:xml:ns:xmpp-session"/></stream:features>, SIZE=315, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null 2015-05-15 07:29:23.501 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-21" to="asengar@dev1/47ce0cc2ec34487f"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"><jid>asengar@dev1/47ce0cc2ec34487f</jid></bind></iq>, SIZE=188, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:29:23.528 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-23" to="asengar@dev1/47ce0cc2ec34487f"/>, SIZE=90, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:29:23.607 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-21" to="asengar@dev1/47ce0cc2ec34487f"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"><jid>asengar@dev1/47ce0cc2ec34487f</jid></bind></iq>, SIZE=188, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:29:23.611 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-23" to="asengar@dev1/47ce0cc2ec34487f"/>, SIZE=90, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:29:23.619 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<iq xmlns="jabber:client" type="result" id="6NXL1-25" to="asengar@dev1/47ce0cc2ec34487f"><query xmlns="jabber:iq:roster"/></iq>, SIZE=127, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:29:23.653 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<presence from="asengar@dev1/47ce0cc2ec34487f" xmlns="jabber:client" id="6NXL1-26" to="asengar@dev1"><c node="http://www.igniterealtime.org/projects/smack" xmlns="http://jabber.org/protocol/caps" hash="sha-1" ver="0dEJo9E722bsfw1EA0UwvhzZxcc="/></presence>, SIZE=256, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=AUTH, TYPE=null 2015-05-15 07:29:23.660 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<presence from="asengar@dev1/47ce0cc2ec34487f" xmlns="jabber:client" id="6NXL1-28" to="asengar@dev1"><c node="http://www.igniterealtime.org/projects/smack" xmlns="http://jabber.org/protocol/caps" hash="sha-1" ver="HD3Oz+JX2Gx+b0ENPu2VNrDWp1A="/></presence>, SIZE=256, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=AUTH, TYPE=null 2015-05-15 07:29:52.824 [Watchdog - c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_34124 Socket[unconnected], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=null, to=null, DATA=<iq from="dev1" type="get" id="tigase-ping" to="asengar@dev1/47ce0cc2ec34487f"><ping xmlns="urn:xmpp:ping"/></iq>, SIZE=113, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=get 2015-05-15 07:30:20.241 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-19" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:test1</body><delivery-error xmlns="http://tigase.org/delivery-error"/></message>, SIZE=240, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:30:20.248 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<iq from="dev1" type="result" id="tigase-ping" to="asengar@dev1/47ce0cc2ec34487f"/>, SIZE=83, XMLNS=null, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=result 2015-05-15 07:30:20.255 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-20" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:1</body><delivery-error xmlns="http://tigase.org/delivery-error"/></message>, SIZE=236, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:30:20.264 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-21" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:2</body><delivery-error xmlns="http://tigase.org/delivery-error"/></message>, SIZE=236, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:30:20.266 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-22" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:3</body><delivery-error xmlns="http://tigase.org/delivery-error"/></message>, SIZE=236, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:30:20.272 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-23" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:4</body><delivery-error xmlns="http://tigase.org/delivery-error"/></message>, SIZE=236, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:30:20.283 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-24" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:5</body><delivery-error xmlns="http://tigase.org/delivery-error"/></message>, SIZE=236, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat 2015-05-15 07:30:20.289 [in_13-c2s] ConnectionManager.writePacketToSocket() FINEST: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, type: accept, Socket: c2s@dev1/216.218.236.91_5222_50.161.80.209_49279 Socket[addr=/50.161.80.209,port=49279,localport=5222], jid: asengar@dev1/47ce0cc2ec34487f, Writing packet: from=sess-man@dev1, to=c2s@dev1/216.218.236.91_5222_50.161.80.209_49279, DATA=<message from="852275@dev1/2101e057de2545e2" xmlns="jabber:client" id="u851d-25" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:6</body><delivery-error xmlns="http://tigase.org/delivery-error"/></message>, SIZE=236, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=chat

And particular excerpts
ns="jabber:client" id="u851d-19" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:test1</bo ns="jabber:client" id="u851d-20" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:1</body>< ns="jabber:client" id="u851d-21" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:2</body>< ns="jabber:client" id="u851d-22" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:3</body>< ns="jabber:client" id="u851d-23" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:4</body>< ns="jabber:client" id="u851d-24" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:5</body>< ns="jabber:client" id="u851d-25" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:6</body><

and:
lns="jabber:client" id="u851d-20" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:1</body> lns="jabber:client" id="u851d-21" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:2</body> lns="jabber:client" id="u851d-22" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:3</body> lns="jabber:client" id="u851d-23" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:4</body> lns="jabber:client" id="u851d-24" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:5</body> lns="jabber:client" id="u851d-25" type="chat" to="asengar@dev1"><body>Shankar Tripathi:#@#:852275:#@#:852275:#@#:6</body>

As you can see each time Tigase maintains stanza order.

Aejaz Muslim wrote:

I tried with adding/removing different sm plugins without success.
Is there a page which has description of which plugins should work well
with each other along with explanation of each plugin's functionality.

Default set of plugins should work in majority of installations. There is no page outlining purpose of each plugin as each name is almost always self-explanatory.
In terms of packet ordering following --queue-implementation may be helpful. However, as I stated above - Tigase sends out packets in the correct order already.

Also, is there a support email address & alternate phone number(I tried
calling (415) 315 9771 but was unable to reach anyone). Please help.

Please note Business Hours (PST) note on the contact page.

Preferred way of communication is through our ticketing system. There are also options for more flexible support options.

Categories: Tigase Forums

Tigase server administration: RE: Tigase XMPP configuration doubt.

Mon, 05/18/2015 - 00:38
<iq from='provisioning.xmpp.iot.teliasonera.com' to='test.client09@xmpp.iot.teliasonera.com' type='set' id='25'><claimed xmlns="urn:xmpp:iot:discovery" jid="test.client08@xmpp.iot.teliasonera.com" nodeId="clayster.cl" sourceId="MeteringTopology" public="false"/></iq>

This stanza looks like it's generated by your (external) component and it's missing resource in the destination FullJID - please see #189 and related changes.

Categories: Tigase Forums

Tigase server development: RE: Unable to resolve class

Mon, 05/18/2015 - 00:35

Thank you Wojciech,
everything is clearer now, and I am going to use the nightly website to download everything I need !

Thank you so much,
Luca

Categories: Tigase Forums

Tigase server development: RE: Import/Export Users

Mon, 05/18/2015 - 00:25

Fernando Augusto Cruz Schorwer wrote:

Hi, thanks for your response, punctually, I need to export users, passwords and friendships from a OpenFire server. Using OpenFire is possible create a .xml with the information, but I need to know if is possible import the xml of Openfire to Tigase

Converter itself should access OpenFire database directly so there shouldn't be a need to export data.

I do not understand how to use the importers, I am very novice using Tigase, and still I don´t know where is saved the User Information.

User information will be save to Tigase database schema, which should be created first. Looking at the converter code it's possible it won't work because it references old tigase configuration (as I mentioned it hasn't been tested for a long time now) so it may require some adjustments. In case there has been changes to the OpenFire schema it's possible to use generic Feeder importer and provide custom SQL queries for retrieval user information.

Categories: Tigase Forums

Tigase server development: RE: Unable to resolve class

Mon, 05/18/2015 - 00:17

Luca Stucchi wrote:

Hi there,

I am experiencing a little problem with a class that is not found. In my tigase-console.log I get
unable to resolve class tigase.vhosts.DomainFilterPolicy

As you can see in the repository such class do exists, however it has moved from tigase.vhosts.DomainFilterPolicy to tigase.vhosts.filter.DomainFilterPolicy

I am using a 7.1.0 snapshot tigase-server.jar compiled in my environment, while the other jars are from a 7.0.1 installation.
Could the fact of having two different version cause a problem like this ?

This shouldn't matter in this particular case (vide above - missing class comes from the tigase-server so it should be included in the binary). However it may happen that you are maybe not on the latest sources or you are trying to execute old script with incorrect package (I've just checked and there are none in the repository referencing tigase.vhosts.DomainFilterPolicy)

How could I get all of the jars for a 7.1.0, even a snapshot since a stable version was not released yet ?

What do you mean? Complete packages are available in the nightlies website, maven snapshots are published in the maven snapshot repository

Categories: Tigase Forums

Tigase server administration: RE: Need Information regarding the Tigase XMPP Libraries that wheth...

Mon, 05/18/2015 - 00:03

Ravish Aggarwal wrote:

yes we are interesting in using the Server, as i mentioned that we need library that could support xmpp Streaming handshake (both DIALBACK, TLS + SASL) and PRESENCE , IM message parsing and From our sample code, we open severSocket on 5269 port and then attach that socket to stream object of xmpp library(provided by your library).

Does we get a sample example of how to use the xmpp server library, like how to open stream, do dialback etc.

Tigase supports XMPP standard hence everything in RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core applies.

Categories: Tigase Forums

Tigase server administration: RE: User hangs in memory

Sun, 05/17/2015 - 23:58

Julia Zashchitina wrote:

3) There was a quick database disconnect, so this probably is related to https://projects.tigase.org/boards/15/topics/4914?r=4987

Does Tigase re-establish connections to the DB afterwards (i.e. are there ESTABLISHED socket connections to the DB seen in the operating system and also shown in the DB statistics?)

9) We used PSI, Miranda and other clients. The user is not able to connect even with the correct password.

I assume that after disconnect in (3) attempts to connect this user yields same exception (NPE in JDBCRepository)?

Categories: Tigase Forums

Tigase server development: RE: Tigase XMPP Server in Ubuntu

Sun, 05/17/2015 - 23:38

ss ss wrote:

I have installed Tigase XMPP server in Ubuntu and I am using Pidgin as a client in windows. So, my question is how to connect Tigase server (Ubunutu) by using pidgin client (Windows)?

You have to specify hostname of the machine you want to connect to (in this case hostname of the Ubuntu server) in the account connection preferences.

Categories: Tigase Forums

Tigase server development: RE: Unordered messages with lost messages & duplication

Sat, 05/16/2015 - 19:54

I tried with adding/removing different sm plugins without success.
Is there a page which has description of which plugins should work well
with each other along with explanation of each plugin's functionality.

Also, is there a support email address & alternate phone number(I tried
calling (415) 315 9771 but was unable to reach anyone). Please help.

Categories: Tigase Forums

Tigase server administration: RE: Tigase XMPP configuration doubt.

Fri, 05/15/2015 - 14:43

Hi Artur

Thanks for you quick response.

Regarding to your questions:

  1. What Tigase server do you use?

7.0.0

  1. Does Tigase run in a cluster mode or in a single mode?

Single mode

  1. Do you have any custom code on the server? If, yes, then more details are necessary.

Yeah we had custom code into our server.

  1. Tigase configuration file.

.CONF

#osgiEnabled=(true|false)

#osgiEnabled=false

OSGI=${osgiEnabled}

USERNAME="tigase"

USERGROUP="tigase"

TIGASE_HOME="/opt/tigase-server"

ENC="-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8"

DRV="-Djdbc.drivers=com.mysql.jdbc.Driver:org.postgresql.Driver:org.apache.derby.jdbc.EmbeddedDriver"

#GC="-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:ParallelCMSThreads=2 -XX:-ReduceInitialCardMarks"

#EX="-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA"

#JMX_REMOTE_IP="-Djava.rmi.server.hostname=0.0.0.0"

JAVA_HOME="/usr/lib/jvm/java-7-openjdk-amd64"

CLASSPATH=""

JAVA_OPTIONS="${GC} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server -Xms100M -Xmx200M -XX:PermSize=32m -XX:MaxPermSize=256m -XX:MaxDirectMemorySize=128m "

TIGASE_PID="/var/run/tigase/tigase.pid"

TIGASE_CONFIG="/etc/tigase/tigase.xml"

TIGASE_OPTIONS=" --property-file /etc/tigase/init.properties "

TIGASE_CONSOLE_LOG="/var/log/tigase/console.log"

.PROPIERTIES

config-type=--gen-config-def --gen-config-comp

--admins=<mailto:--admins=>

--debug=server

--comp-name-1=http

--comp-class-1=tigase.http.HttpMessageReceiver

--user-db = mysql

--user-db-uri = jdbc:mysql://db.iot.elion.ee/tigase?user=tigase&password=tig3498SED

--comp-name-1 = ext

--comp-class-1 = tigase.server.ext.ComponentProtocol

#--external = provisioning.xmpp.iot.elion.ee:2309fu23URdufsdfsfRrr923:listen:5275

--external = provisioning.xmpp.iot.teliasonera.com:2309fu23URdufsdfsfRrr923:listen:5275

--virt-hosts=xmpp.iot.teliasonera.com,xmpp.iot.elion.ee

--ssl-def-cert-domain=xmpp.iot.teliasonera.com

#--sm-plugins=-jabber:iq:register

sess-man/plugins-conf/oauth-consumer-key = 923485ryhfgsdkgkgjdfghle4485Y#FGNBSFDzpqmnfg3

sess-man/plugins-conf/oauth-consumer-secret = 3289rh98rfhiufhe89wfyhwei9fuhweipfuy38925y3495yh34teruhteirghjerbgY#3uz

sess-man/plugins-conf/signed-form-required = true

  1. Tigase logs in debug mode with records including the discussed problem.

The logs that we had regarding to the Tigase when we reproduce the issue says this, how I can setup the debug mode?

2015-05-15 23:16:38.121 [ConnectionOpenThread] XMPPIOService.<init>() WARNING: Problem reading cross domain poicy file: etc/cross-domain-policy.xml

java.io.FileNotFoundException: etc/cross-domain-policy.xml (No such file or directory)

at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.&lt;init&gt;(FileInputStream.java:146) at java.io.FileInputStream.&lt;init&gt;(FileInputStream.java:101) at java.io.FileReader.&lt;init&gt;(FileReader.java:58) at tigase.xmpp.XMPPIOService.&lt;init&gt;(XMPPIOService.java:159) at tigase.server.xmppclient.ClientConnectionManager.getXMPPIOServiceInstance(ClientConnectionManager.java:987) at tigase.server.ConnectionManager$ConnectionListenerImpl.accept(ConnectionManager.java:1359) at tigase.net.ConnectionOpenThread.run(ConnectionOpenThread.java:220) at java.lang.Thread.run(Thread.java:745)
  1. Details about the client side software # Description of your use-case, what do you send to the server and what you expect in return and what you receive that you think is wrong.

I send this to the Tigase server.

15-05-2015 17:44:06 /1248147153-tigase-45<mailto:/1248147153-tigase-45> RowRead <iq id="11" to="/1248147153-tigase-45<mailto:/1248147153-tigase-45>" from="/1248147153-tigase-48<mailto:/1248147153-tigase-48>" xmlns="jabber:client" type="get"><query xmlns="http://jabber.org/protocol/disco#info"/></iq>

15-05-2015 17:44:06 /1248147153-tigase-45<mailto:/1248147153-tigase-45> Message Discovery request.

15-05-2015 17:44:06 /1248147153-tigase-45<mailto:/1248147153-tigase-45> Message Service Discovery response.

15-05-2015 17:44:06 /1248147153-tigase-45<mailto:/1248147153-tigase-45> RowWritten <iq from='/1248147153-tigase-45' to='/1248147153-tigase-48' type='result' id='11'><query xmlns="http://jabber.org/protocol/disco#info"><identity category="client" type="pc" name="Clayster"/><feature var="clayster:metering"/><feature var="clayster:metering#Statistics"/><feature var="http://jabber.org/protocol/disco#info"/><feature var="http://jabber.org/protocol/disco#items"/><feature var="jabber:iq:roster"/><feature var="jabber:iq:version"/><feature var="urn:xmpp:eventlog"/><feature var="urn:xmpp:http"/><feature var="urn:xmpp:iot:concentrators"/><feature var="urn:xmpp:iot:control"/><feature var="urn:xmpp:iot:sensordata"/><feature var="urn:xmpp:xdata:dynamic"/><feature var="vcard-temp"/></query></iq>

And I receive this from the Tigase server.

15-05-2015 17:44:05 provisioning.xmpp.iot.teliasonera.com RowRead <iq id="10" to="provisioning.xmpp.iot.teliasonera.com" from="/1248147153-tigase-48<mailto:/1248147153-tigase-48>" type="set"><mine public="false" xmlns="urn:xmpp:iot:discovery"><str name="CLASS" value="Other"/><str name="KEY" value="6de696a4798e659625f071618b4232653ba02518"/></mine></iq>

15-05-2015 17:44:06 provisioning.xmpp.iot.teliasonera.com Message Ownership claim accepted.

15-05-2015 17:44:06 provisioning.xmpp.iot.teliasonera.com RowWritten <iq from='provisioning.xmpp.iot.teliasonera.com' to='/1248147153-tigase-48' type='result' id='10'><claimed xmlns="urn:xmpp:iot:discovery" jid="<mailto:>" nodeId="clayster.cl" sourceId="MeteringTopology" public="false"/></iq>

15-05-2015 17:44:06 provisioning.xmpp.iot.teliasonera.com Message Queuing outgoing message: Thing Claimed by Owner.. Messages in queue: 1

15-05-2015 17:44:06 provisioning.xmpp.iot.teliasonera.com Message Thing Claimed by Owner.

15-05-2015 17:44:06 provisioning.xmpp.iot.teliasonera.com RowWritten <iq from='provisioning.xmpp.iot.teliasonera.com' to='' type='set' id='25'><claimed xmlns="urn:xmpp:iot:discovery" jid="<mailto:>" nodeId="clayster.cl" sourceId="MeteringTopology" public="false"/></iq>

15-05-2015 17:44:06 provisioning.xmpp.iot.teliasonera.com RowRead <iq id="25" to="provisioning.xmpp.iot.teliasonera.com" from="<mailto:>" type="error"><claimed jid="<mailto:>" public="false" xmlns="urn:xmpp:iot:discovery" sourceId="MeteringTopology" nodeId="clayster.cl"/><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xml:lang="en" xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">The feature is not supported yet.</text></error></iq>

15-05-2015 17:44:06 provisioning.xmpp.iot.teliasonera.com Error Stanza Error: The feature is not supported yet.

In Openfire works good and the behavior is this, this I send to the openfire server:

15-05-2015 17:40:40 /35b2a287<mailto:/35b2a287> RowRead <iq from="/d07a1cfd<mailto:/d07a1cfd>" to="/35b2a287<mailto:/35b2a287>" type="get" id="9"><query xmlns="http://jabber.org/protocol/disco#info"/></iq>

15-05-2015 17:40:40 /35b2a287<mailto:/35b2a287> Message Discovery request.

15-05-2015 17:40:40 /35b2a287<mailto:/35b2a287> Message Service Discovery response.

15-05-2015 17:40:40 /35b2a287<mailto:/35b2a287> RowWritten <iq from='/35b2a287' to='/d07a1cfd' type='result' id='9'><query xmlns="http://jabber.org/protocol/disco#info"><identity category="client" type="pc" name="Clayster"/><feature var="Clayster.HomeApp.Entertainment.ChessApplication"/><feature var="clayster:metering"/><feature var="clayster:metering#Statistics"/><feature var="http://jabber.org/protocol/disco#info"/><feature var="http://jabber.org/protocol/disco#items"/><feature var="jabber:iq:roster"/><feature var="jabber:iq:version"/><feature var="urn:xmpp:eventlog"/><feature var="urn:xmpp:http"/><feature var="urn:xmpp:iot:concentrators"/><feature var="urn:xmpp:iot:control"/><feature var="urn:xmpp:iot:sensordata"/><feature var="urn:xmpp:xdata:dynamic"/><feature var="vcard-temp"/></query></iq>

15-05-2015 17:40:40 /35b2a287<mailto:/35b2a287> RowRead <iq from="discovery.clayster.cl" to="/35b2a287<mailto:/35b2a287>" type="set" id="5"><claimed xmlns="urn:xmpp:iot:discovery" jid="<mailto:>" nodeId="clayster.cl" sourceId="MeteringTopology" public="false"/></iq>

15-05-2015 17:40:40 /35b2a287<mailto:/35b2a287> Message Claimed

15-05-2015 17:40:40 /35b2a287<mailto:/35b2a287> RowWritten <iq from='/35b2a287' to='discovery.clayster.cl' type='result' id='5'></iq>

I receive this from the openfire server

Time Id Type Information

15-05-2015 17:40:40 discovery.clayster.cl RowRead <iq from="/d07a1cfd<mailto:/d07a1cfd>" to="discovery.clayster.cl" type="set" id="8"><mine xmlns="urn:xmpp:iot:discovery" public="false"><str name="CLASS" value="Other"/><str name="KEY" value="6de696a4798e659625f071618b4232653ba02518"/></mine></iq>

15-05-2015 17:40:40 discovery.clayster.cl Message Ownership claim accepted.

15-05-2015 17:40:40 discovery.clayster.cl RowWritten <iq from='discovery.clayster.cl' to='/d07a1cfd' type='result' id='8'><claimed xmlns="urn:xmpp:iot:discovery" jid="<mailto:>" nodeId="clayster.cl" sourceId="MeteringTopology" public="false"/></iq>

15-05-2015 17:40:40 discovery.clayster.cl Message Thing Claimed by Owner.

15-05-2015 17:40:40 discovery.clayster.cl RowWritten <iq from='discovery.clayster.cl' to='/35b2a287' type='set' id='5'><claimed xmlns="urn:xmpp:iot:discovery" jid="<mailto:>" nodeId="clayster.cl" sourceId="MeteringTopology" public="false"/></iq>

15-05-2015 17:40:40 discovery.clayster.cl RowRead <iq from="/35b2a287<mailto:/35b2a287>" to="discovery.clayster.cl" type="result" id="5"/>

15-05-2015 17:40:40 discovery.clayster.cl Message Response to query recevied.

We made a comparison against the open fire server and the TIGASE, and you can see that in the RowWritten from the communication from the server to the client, we do not receive the resourse in the IQ item after the JID.

Tigase: <iq from='provisioning.xmpp.iot.teliasonera.com' to='' type='set' id='25'>

OpenFire:<iq from='discovery.clayster.cl' to='/35b2a287' type='set' id='5'>

Also in the Tigase server we receive a Unsuscribed when we do a presence probe.

Time Id Type Information

15-05-2015 18:28:11 provisioning.xmpp.iot.teliasonera.com Message Sending presence probe.

Time Id Type Information

15-05-2015 18:28:11 provisioning.xmpp.iot.teliasonera.com RowWritten " type="probe"/> Time Id Type Information 15-05-2015 18:28:11 provisioning.xmpp.iot.teliasonera.com RowRead <presence to="provisioning.xmpp.iot.teliasonera.com" from="test.client09@xmpp.iot.teliasonera.com<mailto:test.client09@xmpp.iot.teliasonera.com>" type="unsubscribed"/> We attached the word also that have blue color in the most relevant items. Best Regards and have a nice weekend. -----Mensaje original----- De: support@tigase.org<mailto:support@tigase.org> [mailto:support@tigase.org] Enviado el: jueves, 14 de mayo de 2015 14:07 Asunto: [Tigase XMPP Server - Tigase server administration - msg5036] RE: Tigase XMPP configuration doubt.

Categories: Tigase Forums

Tigase server development: RE: Import/Export Users

Fri, 05/15/2015 - 12:27

Hi, thanks for your response, punctually, I need to export users, passwords and friendships from a OpenFire server. Using OpenFire is possible create a .xml with the information, but I need to know if is possible import the xml of Openfire to Tigase, I do not understand how to use the importers, I am very novice using Tigase, and still I don´t know where is saved the User Information.

Best Regards

/Fernando

-----Mensaje original-----
De: [mailto:]
Enviado el: viernes, 15 de mayo de 2015 4:23
Asunto: [Tigase XMPP Server - Tigase server development - msg5040] RE: Import/Export Users

Categories: Tigase Forums

Tigase server development: Unable to resolve class

Fri, 05/15/2015 - 08:46

Hi there,

I am experiencing a little problem with a class that is not found. In my tigase-console.log I get

Script41.groovy: 35: unable to resolve class tigase.vhosts.DomainFilterPolicy @ line 35, column 1. import tigase.vhosts.DomainFilterPolicy 1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:309) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:927) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:575) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:524) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:279) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:258) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:244) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:202) at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.getScriptClass(GroovyScriptEngineImpl.java:368) at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.compile(GroovyScriptEngineImpl.java:174) at tigase.server.script.Script.init(Script.java:121) ...

I am using a 7.1.0 snapshot tigase-server.jar compiled in my environment, while the other jars are from a 7.0.1 installation.

Could the fact of having two different version cause a problem like this ?
How could I get all of the jars for a 7.1.0, even a snapshot since a stable version was not released yet ?

Thanks in advance,
Luca

Categories: Tigase Forums

Tigase server development: RE: Unordered messages with lost messages & duplication

Fri, 05/15/2015 - 08:22

Sorry for not attaching the log before.
Please find the log attached. I am running
the tigase version 7.1.0-SNAPSHOT-b3870.

A is asengar@dev1
B is 852275@dev1

A sends message "test" to B when online.
B replies with "test1".

Then I disable the network connection for A & B
sends messages, 1,2,3,4,5,6.

After connection is enabled for A, it receives
1,6,4,4,2,6(in this order).

The message body tag has some application specific
data as well but the actual message shown to end
user is after the last ':' character.

Categories: Tigase Forums

Tigase server administration: RE: Need Information regarding the Tigase XMPP Libraries that wheth...

Fri, 05/15/2015 - 02:17

Thanks alot for the provided information:

"Are you asking about Federal Information Processing Standards?"
yes , Does Tigase server library is FIPS compliant ? as we need FIPS compliant library only.

yes we are interesting in using the Server, as i mentioned that we need library that could support xmpp Streaming handshake (both DIALBACK, TLS + SASL) and PRESENCE , IM message parsing and From our sample code, we open severSocket on 5269 port and then attach that socket to stream object of xmpp library(provided by your library).

Actually currently we are using JSO (jabber stream object) ,however it doesnot provide active support and not fully compliant to latest xmpp RFC's and repository is not updated from last 8 years, so need other good xmpp server library.

Does we get a sample example of how to use the xmpp server library, like how to open stream, do dialback etc.

Please call me @ +91-9899987733 , or provide your contact no. if my query is not clear or you need more information. thanks in advance.
Please help us in this.

Regards,
Ravish Aggarwal

Categories: Tigase Forums

Tigase server administration: RE: User hangs in memory

Fri, 05/15/2015 - 02:08

Here’s our use case scenario: this user was registered in Tigase before. After he re-installs client application, our server first tries to register user again (using rest services with add-user script). If there’s a DUPLICATE response from Tigase server, we change user’s password.
Because of user hanging in memory (or some inconsistent user state) there’s a NullPointerException response from Tigase. Neither add-user, change-password or delete-user scripts are working.
1) Please find log file attached for that period (user jid is )
2) DB entry for this user doesn’t seem to differ from other users (with correct behavior).
3) There was a quick database disconnect, so this probably is related to https://projects.tigase.org/boards/15/topics/4914?r=4987
4) Tigase is configured to run in cluster mode but at that time there was only one node running.
5) We do not have any custom code in Tigase server.
6) Database is MySQL 5.6 on Amazon RDS.
7) To properly handle emoji we upgraded Tigase mysql-connector to version 5.1.35 and changed encoding to ‘utf8mb4’.
8) Tigase server version is 7.0.0.
9) We used PSI, Miranda and other clients. The user is not able to connect even with the correct password.

Categories: Tigase Forums

Tigase server development: Tigase XMPP Server in Ubuntu

Fri, 05/15/2015 - 01:36

I have installed Tigase XMPP server in Ubuntu and I am using Pidgin as a client in windows. So, my question is how to connect Tigase server (Ubunutu) by using pidgin client (Windows)?

When I have installed Tigase XMPP server in windows then I am able to connect Tigase XMPP server by using pidgin client in same machine (Locally).

Please help me out.

Thanks in advance.

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