Ok, it looks like there are a few instances of java.util.Timer that
aren't set to run in daemon mode. I've committed changes to HEAD, so
hopefully that resolves the problem.

-James

On Tue, 2005-03-22 at 09:49 -0500, Kumar, Ashok wrote:
> I hope this helps. As I mentioned it is tomcat55 and slide2 with
> J2EESqlserver adapter
> 
> 
> org.apache.catalina.startup.Bootstrap at localhost:2006
>       Thread [main] (Suspended (breakpoint at line 553 in Namespace))
>               Namespace.disconnectServices() line: 553
>               NamespaceAccessTokenImpl.disconnect() line: 348
>               Domain.closeNamespace(NamespaceAccessToken) line: 270
>               WebdavServlet.destroy() line: 316
>               StandardWrapper.unload() line: 1279
>               StandardWrapper.stop() line: 1632
>               StandardContext(ContainerBase).removeChild(Container) line:
> 884
>               StandardContext.removeChild(Container) line: 3019
>               ContextConfig.stop() line: 1007
>               ContextConfig.lifecycleEvent(LifecycleEvent) line: 253
>               LifecycleSupport.fireLifecycleEvent(String, Object) line: 119
>               StandardContext.stop() line: 4262
>               StandardHost(ContainerBase).removeChild(Container) line: 884
>               HostConfig.undeployApps() line: 1120
>               HostConfig.stop() line: 1092
>               HostConfig.lifecycleEvent(LifecycleEvent) line: 312
>               LifecycleSupport.fireLifecycleEvent(String, Object) line: 119
>               StandardHost(ContainerBase).stop() line: 1043
>               StandardEngine(ContainerBase).stop() line: 1055
>               StandardEngine.stop() line: 442
>               StandardService.stop() line: 512
>               StandardServer.stop() line: 2044
>               Catalina.stop() line: 586
>               Catalina.start() line: 561
>               NativeMethodAccessorImpl.invoke0(Method, Object, Object[])
> line: not available [native method]
>               NativeMethodAccessorImpl.invoke(Object, Object[]) line: not
> available
>               DelegatingMethodAccessorImpl.invoke(Object, Object[]) line:
> not available
>               Method.invoke(Object, Object...) line: not available
>               Bootstrap.start() line: 271
>               Bootstrap.main(String[]) line: 409
>       Thread [Timer-0] (Running)
>       Thread [http-8080-Processor1] (Running)
>       Thread [http-8080-Monitor] (Running)
>       Thread [TP-Processor1] (Running)
>       Thread [TP-Processor2] (Running)
>       Thread [TP-Processor3] (Running)
>       Thread [TP-Processor4] (Running)
>       Thread [TP-Monitor] (Running)
>       Thread [http-8080-Processor2] (Running)
> 
> org.apache.catalina.startup.Bootstrap at localhost:1977
>       Thread [Timer-0] (Running)
>       Thread [TP-Processor4] (Running)
>       Thread [http-8080-Processor2] (Running)
>       Thread [DestroyJavaVM] (Running)
> 
> 
> -----Original Message-----
> From: James Mason [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 21, 2005 11:13 PM
> To: Slide Developers Mailing List
> Subject: RE: Slide not properly shutting down
> 
> 
> thread.setDaemon(true);
> 
> Any idea which threads are causing the problems? This should be easy to
> fix.
> 
> -James
> 
> On Mon, 2005-03-21 at 08:10 -0800, Warwick Burrows wrote:
> > I have seen a similar problem. I was told that it is related to how you
> > define your threads to Tomcat. If the thread is a daemon thread then
> > Tomcat needs to know this so that it doesn't wait for the thread to
> > finish when it is trying to shut down your apps threads. I don't know
> > specifically how to do this though.
> > 
> > Warwick
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Kumar, Ashok [mailto:[EMAIL PROTECTED] 
> > > Sent: Monday, March 21, 2005 8:44 AM
> > > To: Slide Developers Mailing List
> > > Subject: Slide not properly shutting down
> > > 
> > > 
> > > We are running Latest Slide2 release under Tomcat55. We are 
> > > noticing a case where tomcat doesnot completly shutdown and 
> > > we see some Slide related threads still lying around. We are 
> > > using the J2EE configuration. Has any  one else seen such a 
> > > behaviour. 
> > > 
> > > Ashok
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > 
> > > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to