interesting, let me know if you still experience this, and I will try to replicate it. It is working fine for me on redhat with 5.0.18.
Filip ----- Original Message ----- From: "Aadi Deshpande" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, February 05, 2004 7:50 AM Subject: Re: problems shutting down server when enabling the SimpleTcpCluster I've definitely noticed this issue on TC 5.0.16 ( though I can't remember if we noticed in 5.0.18, but I am testing that version now ) We're running J2SDK 1.4.1_03 on Solaris 8 , if that's any help. I'm also going to be trying this on J2SDK 1.4.2 with 5.0.18 and I will report back. Again, thanks for any input you can provide, -a Filip Hanik (lists) wrote: >which version of tomcat? the latest? this means that a thread is not a >daemon thread, and the stop will not work. >this was a bug a long time ago. has it resurfaced? > >Filip > >-----Original Message----- >From: Aadi Deshpande [mailto:[EMAIL PROTECTED] >Sent: Monday, February 02, 2004 2:00 PM >To: [EMAIL PROTECTED] >Subject: problems shutting down server when enabling the >SimpleTcpCluster > > > >Hi, > >we have 2 tomcat instances that are clustered via the >SimpleTcpReplication cluster. > >When they start up, i see that they are both communicating and they seem >to be working OK. > >However, whenever I try to shut down an instance using the >$TOMCAT_HOME/bin/catalina.sh script, the server never fully dies. > >It seems like there around 20 threads still hanging around, all doing >something related to persisting these sessions. > >This is in a development instance so we have maybe 4 or 5 sessions at >best at any given time,so I'm not sure why replication would take so long. >These servers hang around forever and can only be killed via a "kill >-9" . Any further attempts to run 'catalina.sh stop' results in the >connection refused error, presumably because the instance has stopped >listening on that port for requests. > >And i know the server is attempting to shut down since i get the >"Unregistering..." messages in my log files. > >Any help is much appreciated, > >Thanks in advance, > >Aadi Deshpande > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >--- >Incoming mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > >--- >Outgoing mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.577 / Virus Database: 366 - Release Date: 2/3/2004 > > >--------------------------------------------------------------------- >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]
