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?
--- 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:16 AM, Ozgur Ozdemircili < ozgur.ozdemirc...@gmail.com> wrote: > Hi, > > The command: > netstat -n grep 8080 | grep CALL_WAIT > > gives me nothing, yet when I update CALL_WAIT with TIME_WAIT I can see > them. > > netstat -n grep 8080 | grep TIME_WAIT > > P.S: Just restarted the servers. As expected the thread counts dropped to > normal. Now I am on 43 Current and 20 Busy. > > > > Özgür Özdemircili > http://www.acikkod.org > Code so clean you could eat off it > > > > > On Fri, Jun 25, 2010 at 11:05 AM, Mick Knutson <mknut...@baselogic.com > >wrote: > > > I am on something right now like this. > > > > While running, Do a: > > netstat -n grep [your port number] | grep CALL_WAIT > > > > See if you are hung in CALL+WAIT status. > > > > --- > > 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 4:01 AM, Ozgur Ozdemircili < > > ozgur.ozdemirc...@gmail.com> wrote: > > > > > 24 > > >
