On Wed, 2003-08-06 at 09:26, Adam Kerrison wrote: > - I have had problems where I had to kill threaded apps when the > code raises an exception. In SOME cases the thread dies and the > application stops responding (depends a lot on how the app is > designed). I don't think I've seen this specifically with Webware but > if the socket handler dies then the other threads will be waiting for > things that will never happen (and the process will be swapped out > eventually). I am assuming a lot about how the AppServer is working - > I don't know that this is right but I'm sure someone will correct > me :-)
The AppServer shouldn't get stuck on a socket -- the socket is passed off to a child thread almost immediately, so whatever happens with the socket shouldn't effect the main thread. Potentially all child threads could be wedged, and this would stall the AppServer. But this fits what we're seeing -- child threads wedge, not the main thread. So it's not impossible that this is happening in AppServer or ThreadedAppServer, and not servlet code. If that's NOT the case, then in the log there should be some request that is started but never finishes: if so then its probably in the servlet code, if not then it's probably inside WebKit. Ian ------------------------------------------------------- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
