RE: LifecycleException
Howdy, This exception happens because server is trying to remove a child element of a container (in this case a StandardContext called TEMPLATE) that has not been started. Chances are there are errors earlier in the log telling you that context could not be started for some reason -- fix that reason and this will go away. As for what a LifecycleException is: see the catalina javadocs at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/catalina/docs/api/index.html. Feel free to write a better document and contribute it ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Jerald Powel [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 12:15 AM To: Tomcat Users List Subject: LifecycleException Hi, Can someone please expand on a log entry LifecycleException (more below), or direct me towards Exception documentation? Thanks alot G LifecycleException: Container StandardContext[/TEMPLATE] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036) .. - BT Yahoo! Broadband - Save £80 when you order online today. Hurry! Offer ends 21st December 2003. The way the internet was meant to be. This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: LifecycleException
I had this same problem yesterday and it was because the manager.xml file was looking in the wrong directory for webapps and once I modified it to work properly, manager loaded and I didn't get the LifecycleException error. There should be another error before the LifecycleException to tell you why your portion of Tomcat wasn't loaded. Hope this helps, Jeremy -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 6:47 AM To: Tomcat Users List Subject: RE: LifecycleException Howdy, This exception happens because server is trying to remove a child element of a container (in this case a StandardContext called TEMPLATE) that has not been started. Chances are there are errors earlier in the log telling you that context could not be started for some reason -- fix that reason and this will go away. As for what a LifecycleException is: see the catalina javadocs at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/catalina/docs/api/index. html. Feel free to write a better document and contribute it ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Jerald Powel [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 12:15 AM To: Tomcat Users List Subject: LifecycleException Hi, Can someone please expand on a log entry LifecycleException (more below), or direct me towards Exception documentation? Thanks alot G LifecycleException: Container StandardContext[/TEMPLATE] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643 ) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1 036) .. - BT Yahoo! Broadband - Save £80 when you order online today. Hurry! Offer ends 21st December 2003. The way the internet was meant to be. This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
Re: LifecycleException when setting up JDBCRealm w postgres 7.2.1
Try looking at your Postgres logs for more information. Edit your postgresql.conf file by setting 'syslog' to 1 or 2. Then check your system logs after you try to start up Tomcat. Other options to consider in your postgresql.conf file: log_connections = true debug_level = 4 debug_pring_query = true -- Robert Abernethy IV Dynamic Edge, Inc. 734.975.0460 Hello, I've had a hard time setting up a JDBCRealm in Tomcat 4.1.18 Win2k connecting to a postgresql 7.2.1 server on a seperate machine. I've set up the server.xml following the directions to a tee: Realm className=org.apache.catalina.realm.JDBCRealm debug=99 driver=org.postgresql.Driver connectionURL=jdbc:postgresql://my.database.com/dbname connectionName=username connectionPassword=password digest=MD5 userTable=users userNameCol=username userCredCol=password userRoleTable=user_roles roleNameCol=role_name / I have copied pg73jdbc2.jar (I've also tried pg73jdbc3.jar) to the common/lib directory I can connect to postgresql through jsp just fine, through simple jdbc just fine. I have searched the mailing list archives and groups.google.com none of the answers seem to apply. I originally had the problem with tomcat 4.1.3 and I upgraded but to no avail. Please help. I get this error message when I start up tomcat with this realm config: Bootstrap: Create Catalina server Bootstrap: Starting service Starting service Tomcat-Standalone Apache Tomcat/4.1.18 Catalina.start: LifecycleException: Exception opening database connection: java.sql.SQLException LifecycleException: Exception opening database connection: java.sql.SQLException at org.apache.catalina.realm.JDBCRealm.start(JDBCRealm.java:681) at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1173) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start (StandardServer.java:2189) at org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:273) 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:324) at org.apache.catalina.startup.BootstrapService.start (BootstrapService.java:245) at org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) - Root Cause - java.sql.SQLException at org.apache.catalina.realm.JDBCRealm.open(JDBCRealm.java:606) at org.apache.catalina.realm.JDBCRealm.start(JDBCRealm.java:679) at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1173) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start (StandardServer.java:2189) at org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:273) 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:324) at org.apache.catalina.startup.BootstrapService.start (BootstrapService.java:245) at org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) Bootstrap: Service started -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: LifecycleException
Hi, -Original Message- From: Bill Saur [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 8:29 PM To: [EMAIL PROTECTED] Subject: RE: LifecycleException Oliver and Anton, I understand the concept of what you are saying but I am in need of practical details. I have checked the server.xml file and the ports shown there are the Tomcat defaults - 8005 for shutdown, and 8080 for the HTTP port. How do I go about checking further? I am not familiar with the command netstat -a, is that a Tomcat command? How do I go about implementing this command? I think you guys are onto something, About that netstat command. Its not Tomcat one. Its standard command for OSes that support TCP/IP. And Win2k surely do, so try Start - Run - cmd in the command window netstat -a You should see the list of ports your host is listening and so on. You can try telnet localhost 8005 and then type there shutdown command from server.xml (default is SHUTDOWN, all caps) to stop Tomcat. And it usually takes some time for Tomcat to stop, so if you're trying to start it before it released to port you're just getting what you should get. I just need some practical elaboration on how to proceed. Thanks again for your help - I am looking to learn from this problem. Bill Saur Spokane, WA [EMAIL PROTECTED] Hope it helps. Anton. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: LifecycleException
All: I solved the problem I was having and I wanted to post the solution in case others may learn from this. Tomcat was not shutting down properly on my computer because of the Microsoft Instant Messaging program that typically runs in my system tray. Until I exited the IM program the connection was held open. I want to thank Anton Brazhnyk, Oliver Lauer, and Ralph Einfeldt for providing me with the information I needed to gain insight into the problem. It was nice of you to take the time to help. So my first experience with the Tomcat Users Mailing List has been good... Bill Saur Spokane, WA [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: LifecycleException
Oliver and Anton, I understand the concept of what you are saying but I am in need of practical details. I have checked the server.xml file and the ports shown there are the Tomcat defaults - 8005 for shutdown, and 8080 for the HTTP port. How do I go about checking further? I am not familiar with the command netstat -a, is that a Tomcat command? How do I go about implementing this command? I think you guys are onto something, I just need some practical elaboration on how to proceed. Thanks again for your help - I am looking to learn from this problem. Bill Saur Spokane, WA [EMAIL PROTECTED] -Original Message- From: Lauer, Oliver [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 12:12 AM To: 'Tomcat Users List' Subject: AW: LifecycleException Yes, it seems TC is still listening and the shutdown didn't work properly ? Have a look at the port that is used for the shutdown. Maybe another thread is using that, so that the shutdown-command doesn't receive TC. Oliver AXA eSolutions GmbH AXA Konzern AG Germany Oliver Lauer Web Architect Wörthstraße 34 D-50668 Köln Germany Tel.: +49 221 148 31277 Fax: +49 221 148 43963 Mobil: +49 179 59 064 59 e-Mail: [EMAIL PROTECTED] _ -Ursprüngliche Nachricht- Von: Anton Brazhnyk [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 28. Januar 2002 09:05 An: Tomcat Users List Betreff: RE: LifecycleException Hi, -Original Message- From: Bill Saur [mailto:[EMAIL PROTECTED]] Sent: Friday, January 25, 2002 11:12 PM To: [EMAIL PROTECTED] Subject: LifecycleException Hello: I have just installed Tomcat 4.0.1 (Win2000 OS) and the program works one time and then once I shut it down and restart it I am getting the following message: Catalina.start: LifecycleException: null.open: java.net.BindException: Address In use: JVM_Bind - followed by a long list of addresses where JVM_Bind is in use. It seems somebody (possibly another Tomcat) is already listening on the port Tomcat tries to bind. Check netstat -a Anyone have any ideas on what is going on here and how to fix this? Thanks in advance for your help. Regards, Bill Saur Spokane, WA [EMAIL PROTECTED] Anton. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: LifecycleException
Thanks Ralph Einfeldt - your post was helpful. So after I run the netstat -a command I get a table that displays the following relevant information: Protocol: TCP Local Address: billsaur:1651 Foreign Address: billsaur:8005 State: TIME_WAIT The port 8005 is the Tomcat default shutdown port and it is occupied in a TIME_WAIT state - this appears to be the reason behind the LifecycleException and JVM_Bind problem I'm experiencing. I have run the shutdown.bat file and it is apparently not working. Any ideas on what's going on and how to get it to shutdown properly and get the port out of the TIME_WAIT state? Bill Saur Spokane, WA [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: LifecycleException
Hi, -Original Message- From: Bill Saur [mailto:[EMAIL PROTECTED]] Sent: Friday, January 25, 2002 11:12 PM To: [EMAIL PROTECTED] Subject: LifecycleException Hello: I have just installed Tomcat 4.0.1 (Win2000 OS) and the program works one time and then once I shut it down and restart it I am getting the following message: Catalina.start: LifecycleException: null.open: java.net.BindException: Address In use: JVM_Bind - followed by a long list of addresses where JVM_Bind is in use. It seems somebody (possibly another Tomcat) is already listening on the port Tomcat tries to bind. Check netstat -a Anyone have any ideas on what is going on here and how to fix this? Thanks in advance for your help. Regards, Bill Saur Spokane, WA [EMAIL PROTECTED] Anton. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
