Nov 14, 2008 10:51:39 AM org.apache.catalina.startup.Catalina start
SEVERE: Catalina.start:
LifecycleException: service.getName(): "Catalina"; Protocol handler start
failed: java.net.BindException: Address already in use:8010
at org.apache.catalina.connector.Connector.start(Connector.java:1139)
at
org.apache.catalina.core.StandardService.start(StandardService.java:457)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
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.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Nov 14, 2008 10:51:39 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 7268 ms
Nov 14, 2008 10:54:37 AM org.apache.catalina.connector.Connector pause
SEVERE: Protocol handler pause failed
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:208)
at
org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:486)
at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:283)
at org.apache.jk.server.JkMain.pause(JkMain.java:681)
at
org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
at org.apache.catalina.connector.Connector.pause(Connector.java:1074)
at
org.apache.catalina.core.StandardService.stop(StandardService.java:489)
at
org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
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.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Nov 14, 2008 10:54:38 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Nov 14, 2008 10:54:38 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
Nov 14, 2008 10:54:38 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextDestroyed()
Nov 14, 2008 10:54:39 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8010
Peter Crowther wrote:
>
>> From: djbowen1 [mailto:[EMAIL PROTECTED]
>> I have the catalina.out and the catalina.date logs.which one is more
>> usefull?
>
> The .out file typically has any errors in it. The logging format is
> similar to many other applications. I'd suggest looking through that for
> error messages - a swift hunt for "xception" in your text editor of choice
> is often remarkably informative!
>
> To find the most recent set of exceptions, go to the end of the file and
> search backwards for "startup". YOu should find a "startup complete"
> line. Anything more recent than that is after the webapp started, but I
> suspect you'll find problems before that - look backwards in the file for
> things that look problematic.
>
> If you're new to Java and Tomcat, one piece of advice: post *full* stack
> traces of any exceptions you need more information about. The "headline"
> exception often has nested exceptions inside it, and it's often the
> innermost one (and hence the bottom one on the stack trace) that's the
> most infomative one. Along the lines of:
>
> FubarException: Couldn't start application
> [... trace...]
> -- nested exception --
> SqlException: Couldn't connect
> [... trace...]
> -- nested exception --
> SocketException: Connection refused
> [... trace...]
>
> As you can imagine, it's a lot easier to diagnose the problem with all of
> that than if we just see the FubarException!
>
> - Peter
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: [email protected]
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Tomcat-webapp-stopped-working%2C-please-help-tp20502550p20503265.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
