..@gmail.com]
> > Subject: Re: Tomcat current thread count
> >
> > Is there any way I can clear the current thread count without
> > restarting tomcat?
>
> Clearing the thread *count* does nothing - you have to actually terminate
> the excess threads.
>
> > The p
> From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> Subject: Re: Tomcat current thread count
>
> Is there any way I can clear the current thread count without
> restarting tomcat?
Clearing the thread *count* does nothing - you have to actually terminate the
excess
it
On Mon, Jun 28, 2010 at 3:26 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> > Subject: Re: Tomcat current thread count
> >
> > Here we go again.
>
> Same comments apply as
> From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> Subject: Re: Tomcat current thread count
>
> Here we go again.
Same comments apply as before:
You have numerous Timer-x threads going, which makes me suspicious that your
webapp is starting up extra threads and
Hi,
Here we go again.
Let`s see if it accepts.
Özgür Özdemircili
http://www.acikkod.org
Code so clean you could eat off it
On Fri, Jun 25, 2010 at 8:04 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Özgür,
>
> On 6/25/201
> From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> Subject: Re: Tomcat current thread count
>
> I have gotten a thread dump using kill -3 .
Don't see anything wrong with the Tomcat threads. As Chris noted, they are all
just waiting for another request to show up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Özgür,
On 6/25/2010 12:21 PM, Ozgur Ozdemircili wrote:
> I probably wont be able to get the one close to crash but the jstack.out
> in the attached file contains the output while the applicaction is
> receiving requests.
>
> Hope it will be more help
Hi,
I probably wont be able to get the one close to crash but the jstack.out in
the attached file contains the output while the applicaction is receiving
requests.
Hope it will be more helpful.
Özgür Özdemircili
http://www.acikkod.org
Code so clean you could eat off it
On Fri, Jun 25, 2010
On 25.06.2010 17:51, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Özgür,
On 6/25/2010 11:39 AM, Ozgur Ozdemircili wrote:
Thanks for the useful link. I have gotten a thread dump using kill -3 .
You can find it in the attached file.
It looks like almost everything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Özgür,
On 6/25/2010 11:39 AM, Ozgur Ozdemircili wrote:
> Thanks for the useful link. I have gotten a thread dump using kill -3 .
>
> You can find it in the attached file.
It looks like almost everything is idle, here. Can you wait a while,
when you
t; > From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> > Subject: Re: Tomcat current thread count
> >
> > What would be the possible ways of finding where the problem lies ?
>
> As previously stated, take a thread dump *before* the JVM crashes and find
> ou
> From: Mick Knutson [mailto:mknut...@baselogic.com]
> Subject: Re: Tomcat current thread count
>
> You can force it by:
>
> set JAVA_OPTS=%JAVA_OPTS%
> -*XX:+HeapDumpOnCtrlBreak*-XX:+HeapDumpOnOutOfMemoryError
No, that gets you a Java heap dump, not a thread dump - not of
> From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> > Subject: Re: Tomcat current thread count
> >
> > What would be the possible ways of finding where the problem lies ?
>
> As previously stated, take a thread dump *before* the JVM crashes and find
>
> From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> Subject: Re: Tomcat current thread count
>
> What would be the possible ways of finding where the problem lies ?
As previously stated, take a thread dump *before* the JVM crashes and find out
what your threads are stu
cili
> http://www.acikkod.org
> Code so clean you could eat off it
>
>
>
>
> On Fri, Jun 25, 2010 at 3:58 PM, Caldarale, Charles R <
> chuck.caldar...@unisys.com> wrote:
>
> > > From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> >
Özgür Özdemircili
http://www.acikkod.org
Code so clean you could eat off it
On Fri, Jun 25, 2010 at 3:58 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> > Subject: Re: Tomcat current thread count
&
> From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
> Subject: Re: Tomcat current thread count
>
> Im actually using Javamelody to monitor the apps.
>
> Yet still nothing. Any ideas ?
Looks like you have two separate problems. The first is that your
Tomcat-conf
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.baselo
Im actually using Javamelody to monitor the apps.
Yet still nothing. Any ideas ?
Özgür Özdemircili
http://www.acikkod.org
Code so clean you could eat off it
On Fri, Jun 25, 2010 at 11:22 AM, Mick Knutson wrote:
> TIME_WAIT is fine. Not an issue. That just means they are ready to take
> requ
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 a
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, Pr
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ü
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: (25
Hi,
In our production enviroment I have a weird problem and I am trying to
understand if / how can it be fixed.
The error is like above:
*
*
*INFO: Maximum number of threads (250) created for connector with address
null and port 8080*
*
*
*
*
*
*
*# A fatal error has been detected by the Java Run
24 matches
Mail list logo
