|
Sanjay Pujare opened 10 years ago
|
|
I found cause of this issue which was related to not registering localdomain-remotedomain as authenticated in some cases and fixed it. Next snapshot build should contain this fix and work as expected. |
|
|
I tested this and I noticed an improvement. For the previous test that was failing it is passing now. However there is one other case where I saw a similar error and I don't understand why that should happen, So for now I am keeping it open. In any case I don't see a way to resolve this. |
|
|
This seems to work now. I could see the following 2 packets going on the same outbound XMPP connection and i.e. same dest domain nxptest.ucinterop.info and different source domains voxbone.com and tatacommunications.com . So will mark it as resolved. |
|
|
I cannot seem to resolve this nor can I reassign this to anyone. Artur or Andrzej: pls treat appropriately |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
3181
|
| Version |
tigase-server-7.1.0
|
| Spent time |
42h
|
We are using 7.1.0 SNAPSHOT and we noticed a problem with multiplexed XMPP S2S connection to Tigase as follows:
NxPFS (my XMPP server) opens an outbound connection to Tigase as follows. Note that this is a single XMPP connection with outbound (NxPFS->Tigase) and inbound (Tigase->NxPFS) stanzas as shown.
NxPFS->Tigase
05:01:57 PM:1:<stream:stream xmlns="jabber:server" xmlns:db="jabber:server:dialback" xmlns:stream="http://etherx.jabber.org/streams" from="voxbone.com" to="nxptest.ucinterop.info" xml:lang="en" version="1.0">
Tigase->NxPFS
05:01:57 PM:2:<stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:server' xmlns:db='jabber:server:dialback' id='ebc1452c-da5f-4b8c-9eb0-6181d7925a26' from='nxptest.ucinterop.info' to='voxbone.com' version='1.0'>
05:01:57 PM:3:stream:features</stream:features>
NxPFS->Tigase
05:01:57 PM:4:<db:result from="voxbone.com" to="nxptest.ucinterop.info">8d7c05b920220395620737ebc1452c-da5f-4b8c-9eb0-6181d7925a26</db:result>
Tigase->NxPFS
05:01:59 PM:9:<db:result from="nxptest.ucinterop.info" to="voxbone.com" type="valid"/>
At this point the connection is valid for sending packets from voxbone.com to nxptest.ucinterop.info and indeed many packets are sent successfully.
After some point NxPFS tries to authenticate this connection for a different pair:
NxPFS->Tigase
05:02:51 PM:63:<db:result from="tatacommunications.com" to="nxptest.ucinterop.info">7580d40d20420395620737ebc1452c-da5f-4b8c-9eb0-6181d7925a26</db:result>
Tigase->NxPFS
05:02:53 PM:68:<db:result from="nxptest.ucinterop.info" to="tatacommunications.com" type="valid"/>
Since the Tigase server came back with “valid” dialback result the connection SHOULD BE valid for sending packets from tatacommunications.com to nxptest.ucinterop.info. However when NxPFS does try to send a packet as follows:
NxPFS->Tigase
05:02:53 PM:69:
We get a stream error back from Tigase and the stream is closed:
Tigase->NxPFS
05:02:53 PM:70:stream:error</stream:error></stream:stream>
If indeed the connection was authenticated for the "tatacommunications.com->nxptest.ucinterop.info” pair, why did it reject the new packet for the same pair?