-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Benimaur,
On 1/3/14, 1:16 AM, Benimaur Gao wrote:
> gotcha! I moved tomcat home directory to another partition by using
> 'cp -r' at that time. That's why tomcat start to reload.
Since you didn't use the "-p" switch, all of your timestamps were
pro
@unisys.com> wrote:
> > From: Benimaur Gao [mailto:benim...@gmail.com]
> > Subject: Re: All worker threads of my tomcat have been occupied!
>
> Don't top post - it makes the conversation very difficult to follow.
>
> > that's very strange. I failed to find any thre
> From: Benimaur Gao [mailto:benim...@gmail.com]
> Subject: Re: All worker threads of my tomcat have been occupied!
Don't top post - it makes the conversation very difficult to follow.
> that's very strange. I failed to find any thread stack relevant to
> tomcat reloadi
@ Chuck
that's very strange. I failed to find any thread stack relevant to tomcat
reloading.
@ Chris
No, I do not use the manager app. All settings in my server.xml are just
using the default value, except one modification to block to set
the real deployment path.
My question is: what's the cond
> From: Benimaur Gao [mailto:benim...@gmail.com]
> Subject: All worker threads of my tomcat have been occupied!
> I tried jstack to get some info, and then I found a lot of thread call
> stack like:
> "http-8082-154" daemon prio=10 tid=0x7f711c21f800 nid=0x5b0a waiting on
> condition [0x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Benimaur,
On 1/2/14, 5:20 AM, Benimaur Gao wrote:
> I found my tomcat refusing to work this morning. I tried jstack to
> get some info, and then I found a lot of thread call stack like:
>
> "http-8082-154" daemon prio=10 tid=0x7f711c21f800 nid=
