Hi everyone - About a week ago, I posted a message describing a problem I've encountered with the IM Server kicking everyone off and refusing to allow connections. The symptoms on the IM Server were that it reported "20 threads in the ThreadPool are busy" and that the IM Server service would not shut down. I have since encountered a couple additional tidbits of information.
1) Yesterday morning, there were 12 threads that were reported busy, but connectivity was still taking place. 2) Yesterday evening, the thread count got up to 19 before the server hung/crashed. 3) The service does not exactly hang. It just takes a really, really, really, really long time to shut down. I tried shutting the service down since it had only reached 19 threads rather than the 20 threads it reached in the past. I figured that I might get lucky. It wasn't shutting down, so I was going to reboot the server, but got distracted for about an hour. In that time, the service had shut down, and I was able to start the service without rebooting the server. The moral? If your IM Server hangs/crashes, and you have an hour to wait for the service to shut down, go for it. Otherwise, killing the process or rebooting the server seems to be the quickest solution. If an Ipswitch software developer would like to see the log file for today, please e-mail me directly and I'll send it along. It's chock full of error messages that might be useful. -Todd To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/ipswitchim_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/Instant_Messenger/index.asp
