Oops. You are correct. I have been up for 2 weeks on this and need to sleep. But that was my issue.
--- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://www.baselogic.com Blog: http://www.baselogic.com/blog/ Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Fri, Jun 25, 2010 at 5:45 AM, Rainer Jung <rainer.j...@kippdata.de>wrote: > On 25.06.2010 11:22, Mick Knutson wrote: > >> TIME_WAIT is fine. Not an issue. That just means they are ready to take >> requests. CALL_WAIT is not good, if they stick around. >> If this is an OOM error, then have you started this server and attached >> javaVisualVM onto it to see what the threads and memory are doing? >> > > Not judging on whether that's the right approach, but you probably meant > CLOSE_WAIT. There is no TCP state CALL_WAIT. > > Regards, > > Rainer > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
