We are running JBoss 3.2.3 and are having a similar problem that seems to be causing JBoss to periodically max out the CPU on the server thus causing our applications to get very sick.
It seems to me that JBoss should clean up with the 'reset' and not be so critical of a client-side connection that may or may not close properly. Given that a client machine may crash on its own the connection may never get closed properly. Shouldn't the app server expect this from a client? It's easy to say "bad, bad client", but client code is not likely to be as robust as server code even though we all wish it were. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825974#3825974";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825974>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
