Hey,
I have mod_muc installed and application using it in the following way:
- there are many users joining different muc_rooms.
- there is one user (bot) joining every single room
mod_muc config looks like this:
{mod_muc, [
{host, "conference.@HOST@"},
{access, muc},
{access_create, muc},
{access_persistent, muc},
{access_admin, muc_admin},
{max_users, 5000},
{max_user_conferences, 500}
]},
Which is far more that current values.
the problem I'm running into is at some point this happens:
=INFO REPORT==== 2010-03-18 21:32:51 ===
I(<0.32119.0>:ejabberd_c2s:1351) : ({socket_state,tls,{tlssock,#Port<0.40209>,#Port<0.40211>},<0.32118.0>}) Close session for app@xmpp.myserver.com/13369913471268935779485195
The next time I want to send something from the app, I'm getting socket error:
(this is from Ruby client)
I, [03/18 21:33:00 #10548] INFO -- : Exception: #
Timing would suggest that the connection is closed on ejabberd side, as there is no action on application side at that (but there is some just before, let's say messaging 12 different rooms within 10 sec period)
Is there a possibility ejabberd would remove my app user from the server without communicating a reason?
Thanks for your help,
Krzysztof
krist0ff wrote: Timing would
Timing would suggest that the connection is closed on ejabberd side, as there is no action on application side at that (but there is some just before, let's say messaging 12 different rooms within 10 sec period)
Yes, there are several reasons ejabberd may close a client connection. In some cases it sends an error stanza to the client just before closing its connection.
Try to sniff the network traffic (using Wireshark, tcpflow, ...) to see what are the last stanzas in the connection. You can also increase the ejabberd loglevel, maybe you see something useful just before the connection close.
If you find something that looks interesting but you don't know to interpret it exactly, you can paste here it.