Projects tigase _server server-core Issues #1328
IQ-ping result packets seems to be handled incorrectly which results in infinite loop (#1328)
Closed
wojciech.kapcia@tigase.net opened 2 years ago
[2022-06-22 08:59:10.640] [TRACE] [ in_0-message-router] tigase.server.MessageRouter.processPacket(): Processing packet: from=s2s@ip-172-31-38-91.us-west-2.compute.internal, to=null, serverAuthorisedStanzaFrom=Optional.empty, DATA=<iq xmlns="jabber:client" id="png-4d161c94-75d0-4099-89e5-fa504b9c0c58" from="…@loxot.eu/movimMGLbHR" type="result" to="tigase@mix.tigase.im"><ping xmlns="urn:xmpp:ping"/></iq>, SIZE=181, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=REMOTE, TYPE=result, STABLE_ID=null

[2022-06-22 08:59:10.640] [TRACE] [ in_0-message-router] tigase.server.MessageRouter.processPacket(): 1. Packet will be processed by: mix@ip-172-31-38-91.us-west-2.compute.internal, from=s2s@ip-172-31-38-91.us-west-2.compute.internal, to=null, serverAuthorisedStanzaFrom=Optional.empty, DATA=<iq xmlns="jabber:client" id="png-4d161c94-75d0-4099-89e5-fa504b9c0c58" from="…@loxot.eu/movimMGLbHR" type="result" to="tigase@mix.tigase.im"><ping xmlns="urn:xmpp:ping"/></iq>, SIZE=181, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=REMOTE, TYPE=result, STABLE_ID=null

[2022-06-22 08:59:10.641] [TRACE] [            in_3-mix] tigase.cluster.ClusterConnectionManager.executeCommand(): Called fromNode: null, visitedNodes: null, data: null, packets: [<cluster xmlns="tigase:cluster" id="cl-23419185" from="s2s@ip-172-31-38-91.us-west-2.compute.internal" pr="HIGH" type="set" to="mix@ip-172-31-0-99.us-west-2.compute.internal"><control><visited-nodes><node-id>s2s@ip-172-31-38-91.us-west-2.compute.internal</node-id></visited-nodes><method-call name="mix-packet-forward-pubsub-cmd"><par name="perm">REMOTE</par></method-call><first-node>s2s@ip-172-31-38-91.us-west-2.compute.internal</first-node></control><data><iq xmlns="jabber:client" id="png-4d161c94-75d0-4099-89e5-fa504b9c0c58" from="…@loxot.eu/movimMGLbHR" type="result" to="tigase@mix.tigase.im"><ping xmlns="urn:xmpp:ping"/></iq></data></cluster>]
[2022-06-22 08:59:10.641] [TRACE] [            in_3-mix] tigase.cluster.ClusterElement.<init>(): Parsing cluster element: <cluster xmlns="tigase:cluster" id="cl-23419185" from="s2s@ip-172-31-38-91.us-west-2.compute.internal" pr="HIGH" type="set" to="mix@ip-172-31-0-99.us-west-2.compute.internal"><control><visited-nodes><node-id>s2s@ip-172-31-38-91.us-west-2.compute.internal</node-id></visited-nodes><method-call name="mix-packet-forward-pubsub-cmd"><par name="perm">REMOTE</par></method-call><first-node>s2s@ip-172-31-38-91.us-west-2.compute.internal</first-node></control><data><iq xmlns="jabber:client" id="png-4d161c94-75d0-4099-89e5-fa504b9c0c58" from="…@loxot.eu/movimMGLbHR" type="result" to="tigase@mix.tigase.im"><ping xmlns="urn:xmpp:ping"/></iq></data></cluster>
[2022-06-22 08:59:10.641] [TRACE] [    pool-36-thread-3] tigase.cluster.ClusterConnectionManager.processSocketData(): Processing socket data: from=null, to=null, serverAuthorisedStanzaFrom=Optional.empty, DATA=<route from="tigase@mix.tigase.im" pr="NORMAL" perm="NONE" to="s2s@ip-172-31-38-91.us-west-2.compute.internal"><iq xmlns="jabber:client" id="png-1e1e674b-6fff-4327-81f9-ab0ba44499ee" from="tigase@mix.tigase.im" type="error" to="…@loxot.eu/movimMGLbHR"><ping xmlns="urn:xmpp:ping"/><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq></route>, SIZE=409, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null, STABLE_ID=null
[2022-06-22 08:59:10.641] [DEBUG] [      out_11-cl-comp] tigase.cluster.ClusterConnectionManager.processOutPacket(): Unexpected packet on cluster connection: from=tigase@mix.tigase.im, to=s2s@ip-172-31-38-91.us-west-2.compute.internal, serverAuthorisedStanzaFrom=Optional.empty, DATA=<iq xmlns="jabber:client" id="png-1e1e674b-6fff-4327-81f9-ab0ba44499ee" from="tigase@mix.tigase.im" type="error" to="…@loxot.eu/movimMGLbHR"><ping xmlns="urn:xmpp:ping"/><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>, SIZE=290, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=error, STABLE_ID=null
…


[2022-06-22 08:59:10.648] [TRACE] [    pool-36-thread-7] tigase.cluster.ClusterConnectionManager.processSocketData(): Processing socket data: from=null, to=null, serverAuthorisedStanzaFrom=Optional.empty, DATA=<route from="tigase@mix.tigase.im" pr="NORMAL" perm="NONE" to="s2s@ip-172-31-38-91.us-west-2.compute.internal"><iq xmlns="jabber:client" id="png-4d161c94-75d0-4099-89e5-fa504b9c0c58" from="tigase@mix.tigase.im" type="error" to="…@loxot.eu/movimMGLbHR"><ping xmlns="urn:xmpp:ping"/><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq></route>, SIZE=409, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null, STABLE_ID=null
[2022-06-22 08:59:10.648] [DEBUG] [      out_11-cl-comp] tigase.cluster.ClusterConnectionManager.processOutPacket(): Unexpected packet on cluster connection: from=tigase@mix.tigase.im, to=s2s@ip-172-31-38-91.us-west-2.compute.internal, serverAuthorisedStanzaFrom=Optional.empty, DATA=<iq xmlns="jabber:client" id="png-4d161c94-75d0-4099-89e5-fa504b9c0c58" from="tigase@mix.tigase.im" type="error" to="…@loxot.eu/movimMGLbHR"><ping xmlns="urn:xmpp:ping"/><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>, SIZE=290, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=error, STABLE_ID=null
wojciech.kapcia@tigase.net commented 2 years ago

Most likely same issue as in #issue #1282

Andrzej Wójcik (Tigase) commented 2 years ago

Moved to tigase-server as this issue is casued by error generated by StanzaProcessor responding with an error on unexpected stanza (even for type result).

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
Version
tigase-server-8.3.0
Spent time
3h 30m
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#1328
Please wait...
Page is in error, reload to recover