2014-02-17 2:16 GMT+04:00 Tim Leung <timleung1...@gmail.com>: > Can someone please help me? > > > On Sun, Feb 16, 2014 at 12:05 PM, Tim Leung <timleung1...@gmail.com> wrote: >> >> "main" prio=5 tid=7fe82c001800 nid=0x10448e000 runnable [10448b000] >> java.lang.Thread.State: RUNNABLE >> at sun.security.pkcs11.wrapper.PKCS11.C_GetSlotList(Native Method) >> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:314) >> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:86) >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) >> at >> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) >> at >> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) >> at java.lang.reflect.Constructor.newInstance(Constructor.java:513) >> at sun.security.jca.ProviderConfig$4.run(ProviderConfig.java:262) >> at java.security.AccessController.doPrivileged(Native Method) >> at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:244) >> at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:224) >> - locked <7f42b0110> (a sun.misc.Launcher$AppClassLoader) >> at sun.security.jca.ProviderList.loadAll(ProviderList.java:264) >> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:281) >> at sun.security.jca.Providers.getFullProviderList(Providers.java:129) >> - locked <7fb0bfef0> (a java.lang.Class for sun.security.jca.Providers) >> at java.security.Security.getProviders(Security.java:421) >> at >> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:407) >> at >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> at >> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >> at >> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) >> - locked <7f42b6328> (a org.apache.catalina.core.StandardServer) >> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:99) >> - locked <7f42b6328> (a org.apache.catalina.core.StandardServer) >> at org.apache.catalina.startup.Catalina.load(Catalina.java:639) >> at org.apache.catalina.startup.Catalina.load(Catalina.java:664) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455) >>
Wait awhile, take several thread dumps and look whether there is any change in state of the "main" thread. If "main" thread has reached "StandardServer.await()" then you can shutdown Tomcat gracefully. If it has not, graceful shutdown is not possible, as it does not yet listen on the shutdown port. If there is no change, then at this point (in JreMemoryLeakPreventionListener) nothing has really started yet and there is no need in "grace" shutdown. Cannot say anything about PKCS11. Does it always hang there? (It is possible to skip that step in JreMemoryLeakPreventionListener by setting tokenPollerProtection="false", but docs say that the same initialization will happen later, when generating session ids. http://tomcat.apache.org/tomcat-7.0-doc/config/listeners.html ) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
