01062114452200.00649@obelix">Hi,
I have a bot running as a client on the Jabber 1.4 server
(with the conference.0.4.1 module installed). The bot is a
Java app connected to the server via
JabberBeans-0.9.0-pre4.
The first time the bot gets a message, it gets kicked off
of the groupchat. Kind of looks like the socket gets
closed when the groupchart server tries to deliver the
message, although the message does apparently get through.
Could this be bad jabber karma?
I'm attaching a whittled-down snippet of the jabberd debug
output. TIA
=BillThu Jun 21 13:48:22 2001 client.c:248 io_select Socket 13 close notification
Thu Jun 21 13:48:22 2001 deliver.c:460 DELIVER 4:expertq.com <route type='error' to='[EMAIL PROTECTED]/8222E78' from='13@c2s/8241268'/>
Thu Jun 21 13:48:22 2001 deliver.c:649 delivering to instance 'sessions'
Thu Jun 21 13:48:22 2001 deliver.c:83 (80D4178)incoming packet <route type='error' to='[EMAIL PROTECTED]/8222E78' from='13@c2s/8241268'/>
Thu Jun 21 13:48:22 2001 users.c:137 js_user([EMAIL PROTECTED],81554E0)
Thu Jun 21 13:48:22 2001 sessions.c:148 end 136457848 'Di! sconnected'
Thu Jun 21 13:48:22 2001 mio.c:354 freed MIO socket
Thu Jun 21 13:48:22 2001 mtq 8166E50 entering from pth
Thu Jun 21 13:48:23 2001 mtq 8166E50 queue call 8222E78
Thu Jun 21 13:48:23 2001 sessions.c:318 THREAD:SESSION exiting
It looks like the client is disconnecting, not the server - the c2s component is sending a message to JSM (expertq.com) saying that the socket is closed.
Other than this - no clue
-David Waite
01062114452200.00649@obelix">
