Another thought (a long shot) - if your tomcat service is running chrooted or in a more complicated linux/unix virtualization environment, running a script to stop a service on the host machine (i.e. outside one of the containers) can have unintended side-effects on instances of the same service running in the containers. Confused the heck out of me when it happened on my dev box.
Jonathan Essex Consultant, Professional Services Misys Solutions for Banking 63 boulevard Hausmann 75008 Paris, France -----Original Message----- From: Sheldon Ross [mailto:[email protected]] Sent: 16 November 2009 19:55 To: [email protected] Subject: RE: Weird Tomcat issue. Thanks for all the suggestions. I'll definitely be considering/investigating each one. This gives me some places to start, I'll report back when I get it sorted. Thanks Sheldon Ross > Date: Mon, 16 Nov 2009 12:29:58 -0600 > From: [email protected] > To: [email protected] > Subject: Re: Weird Tomcat issue. > > A few other things... > > Have you recently upgraded Java on the server, or been applying patches? > > > Sheldon Ross wrote: > > Tomcat is shutting down. There are no java processes on the server after this happens. The machine itself is still up and running fine. > > > > The servers are secured on a Linux machine behind a firewall. > > > > The auth.logs show noone logging/sshing in when the shutdown occurs. > > > > I'm using an Apache front end and using modjk to connect to Tomcat. > > > > Like I said it's really weird. > > > > I've sort of remedied it by putting "ps -e | grep java || /etc/init.d/tomcat start" in crontab > > But as you can imagine that is far less than Ideal. > > > > > >> Date: Mon, 16 Nov 2009 11:27:07 -0600 > >> From: [email protected] > >> To: [email protected] > >> Subject: Re: Weird Tomcat issue. > >> > >> When you say "it" is shutting down, are you referring to tomcat, or to > >> Turbine. > >> > >> What version of Tomcat and Turbine? > >> > >> When this happens can you still directly reference "any" ports on the > >> tomcat server. (say port 80, etc) > >> > >> What environment are you running it on (Linux, Windows) > >> > >> Are you using the connector? > >> > >> Things don't typically just start happening without a reason... so is > >> access to this server controlled? Is it only you accessing it, your > >> team, etc? Can you pinpoint an approximate time that it started happening? > >> > >> > >> Sheldon Ross wrote: > >> > >>> I just recently started having this weird issue with Tomcat and Turbine. > >>> It appears like its just shutting down cleanly, only we are NOT shutting it down. > >>> > >>> It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. > >>> > >>> Any thoughts? > >>> > >>> Servlet log: > >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 > >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp ] - Stopping filters > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() > >>> > >>> Turbine log: > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService > >>> 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService > >>> 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService > >>> 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService > >>> 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! > >>> > >>> > >>> > >>> > >>> > >>> _________________________________________________________________ > >>> Hotmail: Trusted email with Microsoft's powerful SPAM protection. > >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ > >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ > >>> > >>> > >>> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > _________________________________________________________________ > > Bing brings you maps, menus, and reviews organized in one place. > > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=T EXT_MFESRP_Local_MapsMenu_Resturants_1x1 > > > _________________________________________________________________ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/ "Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027. Registered office: One Kingdom Street, London W2 6BL, United Kingdom. For a list of Misys group operating companies please go to http://www.misys.com/corp/About_Us/misys_operating_companies.html. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
