Project

General

Profile

Exception during packet processing

channa bandara
Added almost 4 years ago

I have successfully deployed Tigase XMPP server in cluster mode. But when I check the log I found the following error in Tigase main server log file.

Exception during packet processing: from=sess-man@ip-172-30-1-226.ap-southeast-1.compute.internal, to=c2s@ip-172-30-1-226.ap-southeast-1.compute.internal/172.30.2.30_5222_118.201.42.139_41889, DATA=<presence to="8618583395352@im.ncs/Onechat" from="47891175-eeab-4c79-820a-dfe43bc7ee77@muc.im.ncs/8618583395352@im.ncs" type="unavailable" xmlns="jabber:client"><x xmlns="http://jabber.org/protocol/muc#user"><item nick="8618583395352@im.ncs" jid="8618583395352@im.ncs/Onechat" affiliation="admin" role="moderator"/><status code="110"/></x></presence>, SIZE=350, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=AUTH, TYPE=unavailable
java.lang.NullPointerException

And when I check the Tigase MUC logs I found the following error, actually which is not related to the above issue.

AbstractComponent.processPacket()  SEVERE:   java.lang.RuntimeException: java.lang.NullPointerException when processing from=null, to=null, DATA=<iq type="set" to="37fd208b-9b89-494f-9c84-dd6e2108f891@muc.im.ncs" xmlns="jabber:client" from="6593793466@im.ncs/Onechat" id="76077040-1A5F-4954-A4E1-678B5BA88CFD"><query xmlns="http://jabber.org/protocol/muc#admin"><item affiliation="none" jid="6592299449@im.ncs"/><item role="none" jid="6592299449@im.ncs"/></query></iq>, SIZE=323, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=set

Can I ignore these error messages? If not how can I fix those errors? Thanks.


Replies (1)

Added by Wojciech Kapcia TigaseTeam almost 4 years ago

channa bandara wrote:

I have successfully deployed Tigase XMPP server in cluster mode. But when I check the log I found the following error in Tigase main server log file.

Please provide full StackTrace from this NPE

And when I check the Tigase MUC logs I found the following error, actually which is not related to the above issue.

Can I ignore these error messages? If not how can I fix those errors? Thanks.

Well, those should be addressed but you should either enable more extensive debugging or provide full StackTraces as well as used Tigase version and configuration.

    (1-1/1)