session not authorized

kellogs .
Added almost 5 years ago


2-clulster deployment, tsunging with:

Getting about two or three such entries per second of

2014-06-02 03:49:54.183 [presence Queue Worker 11]  Presence.process()        INFO:     Can not access user Roster, user session is not authorized yet: from=null, to=sess-man@server1.domain.our, DATA=<presence xmlns="jabber:client" from="+3913256@domain.our/tsung" to="+3913257@domain.our" id="639754" type="unavailable"/>, SIZE=136, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=NONE, TYPE=unavailable

No heavy logging (INFO level), no server strain. Version is based on

commit 48635d0a30a0a28e062b8da33a3d6f8453418866

Author: Wojciech Kapcia <…>

Date: Wed Feb 12 17:28:44 2014 +0100

tigase-server-5.2.0 release

Help! Thanks!

Replies (1)


Added by Artur Hefczyc TigaseTeam almost 5 years ago

Maybe tsung sends a roster request before it gets authenticated? I am not sure whether Tsung even waits for and check the authentication result or just sends next stuff right away. Maybe you should add more thinktime between authentication and roster retrieval request in your Tsung configuration?