Tigase stops responding to new incoming (BOSH) connections after a while
We found sometime tigase stops respond to new incoming connection requests and have lots of warning logs like this:
I wonder what does this mean? It is possible that our server is overloaded, but is there any way to tell from tigase logs like to get a clue of what's going on and how to trouble shoot?
No response within time limit received for a packet: from=null, to=null, DATA= <iq type="set" to="firstname.lastname@example.org" id="8fffd0b5-6ebf-4766-a6d0-eff75f976742" from="email@example.com/12819178-97c8-48f7-9004-4f8f4b2bcb22"> <command node="STREAM_OPENED" xmlns="http://jabber.org/protocol/commands"> <x type="submit" xmlns="jabber:x:data"> <field var="session-id"> <value>82d7e5ad-d9e7-4f1c-b22b-161d197b91f0</value> </field> <field var="hostname"> <value>sumilux.com</value> </field> <field var="xml:lang"> <value>en</value> </field> </x> </command> </iq>
Added by Artur Hefczyc over 4 years ago
It is hard to tell from a single log line why this happens. This line signals a problem but for tracking the problem down to source more information is necessary. The server version, OS, Tigase config files, more log lines of what happens in the SM, also Tigase statistics and metrics are needed as well. Without all the details it is even impossible to guess.