@ 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 <Context> block to set the real deployment path. My question is: what's the condition to trigger tomcat redeployment, and how to avoid it? after all, I don't think it's a proper setting for online server. Does it leave me no choice but upgrading my tomcat? On Fri, Jan 3, 2014 at 2:16 AM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > 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=0x00007f711c21f800 nid=0x5b0a waiting > on > > condition [0x00007f70dc887000] > > java.lang.Thread.State: TIMED_WAITING (sleeping) > > at java.lang.Thread.sleep(Native Method) > > at > > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:132) > > > It seems all of the 200 JIoEndpoint$Worker threads had been occupied. > > > It seems context had been set to reload state at some time, but I can't > > figure out under what circumstance would put tomcat into such state. > > Try looking at the threads _not_ doing the wait from StandardContextValve; > one of those should be involved in reloading the webapp and perhaps you can > find out what it's waiting for. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail and > its attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
