Project

General

Profile

Connection ID not set for this session

Daniele Ricci
Added about 4 years ago

Hi again,

I got this error in tigase-console.log.

2015-01-13 22:20:47.731 [kontalk:jabber:iq:register Queue Worker 0]  SessionManager$ProcessorWorkerThread.process()  WARNING: Exception during packet processing: from=c2s@localhost/198.211.127.209_5999_89.101.85.127_58241, to=sess-man@localhost, DATA=<iq type="error" id="x0XG4-35" from="45b5ed7610ca7e06487572bdb556aacf92ef3775@beta.kontalk.net/8c1ac3ff9c13e9cb" to="beta.kontalk.net" xmlns="jabber:client"><query xmlns="jabber:iq:register"><x xmlns="jabber:x:data" type="form"><field type="hidden" var="FORM_TYPE"><value>CData size: 41</value></field><field type="text-single" label="Signed public key" var="publickey"><value>CData size: 1980</value></field></x></query><error code="404" type="wait"><recipient-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>, SIZE=2523, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=error
tigase.xmpp.NoConnectionIdException: Connection ID not set for this session. This is probably the SM session to handle traffic addressed to the server itself. Or maybe it's a bug.
        at tigase.xmpp.XMPPResourceConnection.getConnectionId(XMPPResourceConnection.java:612)
        at org.kontalk.xmppserver.KontalkIqRegister.process(KontalkIqRegister.java:190)
        at tigase.server.xmppsession.SessionManager$ProcessorWorkerThread.process(SessionManager.java:2885)
        at tigase.util.WorkerThread.run(WorkerThread.java:132)

Does this simply mean that the connection was abruply closed in the meantime or might it be another kind of problem?

Thanks

--

Daniele


Replies (3)

Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam about 4 years ago

Yes, this may mean that the connection was broken.

Adnrzej, could you please confirm. I remember that the code from the time before XEP-198 (Stream management) implementation, simply dropped such packets. I guess with the XEP-198 the connection manager may return an error.

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam about 4 years ago

This is addition to XEP-0198 Stream Management but not strictly related as now if ConnectionManager receives packet for connection which is already closed then it returns it back to SessionManager for processing (ie. to store to offline storage in case of message stanzas) and in some cases (as here broken connection not authorized connection) Connection ID may not be set.

Added by Daniele Ricci about 4 years ago

Thank you!

    (1-3/3)