Thanks for the quick response Gato.
I’'m not sure the subject is our real problem now. It may just be another side-effect of our problem. I am still trying to investigate what the problem is.
But yes, our client service is using the GroupChat class to connect to the MUC service in Messenger.
We are running Jive Messenger 2.1.2.
The rooms are persistent.
We have the Log Messages option enabled.
We have the number of history to display in each room set to 100 messages for returning members.
Everything seemed to be working okay for a couple of days. I just left our overseas offices and came home. Over the weekend they reported that they could not get the computer services to reconnect to any of the GroupChat rooms. When they stop our services, and re-start them, they see the computer user log into the chat room, and immediately leave now. This does not coincide with what I was reporting originally. So I’'m sorry if I am mistaken. It is difficult for me to see what they are experiencing now that I am gone and we 14 hour difference in time.
There are errors being reported on our client service about a broken pipe. I wont be able to get the exact error logs for a couple of days.
In the meantime I have told our system admins to disable the log history option, and truncate the mucConverstationLog table and restart the server. We are crossing our fingers to see what happens until I am able to better reproduce the exact problem in our labs.
I can try to get permission to release our code that is making the connections and sending the messages if that might help. We did not start having these issues until we upgraded to 2.1.2 from 2.1.1 of Jive Messenger. At the same time, I remember seeing changes to our code to handle exceptions and disconnections better. So the real cause is not clear yet.