Not able to create Chat group simultaneously using multiple clients (#620)

Activities

Vijay Kaimal opened 9 years ago

Due Date
2015-12-31

When we try to create Chat Groups simultaneously using multiple clients( agsXMPP - Matrix), we are getting error and not all the chat groups are getting created.Please find the attached init.properties and log files.

I am using the nightly build from December 10,2015 (tigase-issue #7.1.0-SNAPSHOT-b4109)

Error Description : -

We tried to create the following sets of persistent chat groups simultaneously. (each set was having 25 chat groups with numbers 0 to 24 added as suffix) : -

"TEST_IE0" ,"TEST_IE1", .... to...., "TEST_IE24"
**"TEST-MOZILLA0", "TEST-MOZILLA1",........to........., "TEST-MOZILLA24"
**"TEST-CHROME0", "TEST-CHROME1",....to......., "TEST-CHROME24"

Only "TEST-MOZILLA0" and "TEST_IE0" ,"TEST_IE1", .... to...., "TEST_IE24" got created.

init.properties

Vijay Kaimal commented 9 years ago

Please note, from all the clients we have logged in as the same user i.e. Tigase admin.

Andrzej Wójcik (Tigase) commented 9 years ago

I checked logs of Tigase XMPP Server which are full of following errors:

2016-01-01 10:25:28.592 [in_0-c2s]         ClientConnectionManager.processCommand()  FINEST: Sending stream close to the client: <stream:error><conflict xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error></stream:stream>

which means that this is error within your clients which most propably in some cases same JID (with same resource) is used by 2 or more clients which is forbidden and Tigase XMPP Server closes one of clients connections using same full JID.

And also following errors:

2016-01-01 10:25:28.204 [in_0-c2s]         ConnectionManager.writePacketToSocket()  FINEST: c2s@chargemeserver/104.130.164.51_5222_202.83.46.164_45951, type: accept, Socket: c2s@chargemeserver/104.130.164.51_5222_202.83.46.164_45951 Socket[addr=/202.83.46.164,port=45951,localport=5222], jid: null, Writing packet: from=sess-man@chargemeserver, to=c2s@chargemeserver/104.130.164.51_5222_202.83.46.164_45951, DATA=<presence xmlns="jabber:client" type="error" id="589ep-3"><error code="401" type="auth"><not-authorized xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xml:lang="en" xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">You must authenticate session first, before you can send any message or presence packet.</text></error></presence>, SIZE=327, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=LOCAL, TYPE=error

which means that client send presence to XMPP server on not authorized connection - maybe it is not waiting for authentication or authentication fails.

In both cases Tigase XMPP Server properly handles each case.

Please verify you clients code.

Artur Hefczyc commented 9 years ago

No feedback, assuming this is not a bug in Tigase.

Type	Bug
Priority	Blocker
Assignee	Vijay Kaimal
RedmineID	3799
Version	tigase-server-7.1.0
Spent time	2h 30m

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#620