File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat Coyote getting paused/stopped/destroyed after restart ??- Error 503

 
Santhosh Ganesan
Greenhorn
Posts: 2
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
here I am posting the logs, Coyote Http1./1 is getting paused after few mins of restart

Jul 1, 2010 3:09:46 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.
Jul 1, 2010 3:09:47 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/server:/usr/jdk/instances/jdk1.5.0/jre/lib/sparc:/usr/jdk/instances/jdk1.5.0/jre/../lib/sparc:/usr/lib:/usr/local/lib:/usr/local/ssl/lib:/usr/lib
Jul 1, 2010 3:09:47 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8013
Jul 1, 2010 3:09:48 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8543
Jul 1, 2010 3:09:48 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8544
Jul 1, 2010 3:09:48 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2432 ms
Jul 1, 2010 3:09:48 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jul 1, 2010 3:09:48 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Jul 1, 2010 3:09:51 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8013
Jul 1, 2010 3:09:51 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8543
Jul 1, 2010 3:09:51 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8544
Jul 1, 2010 3:09:51 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8510
Jul 1, 2010 3:09:51 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/51 config=null
Jul 1, 2010 3:09:51 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2874 ms


Jul 1, 2010 3:23:12 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8013
Jul 1, 2010 3:23:12 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8543
Jul 1, 2010 3:23:12 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8544
Jul 1, 2010 3:23:13 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Jul 1, 2010 3:23:13 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8013
Jul 1, 2010 3:23:13 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8543
Jul 1, 2010 3:23:13 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8544

and its throwing 503 error for the application when accessed

Kindly advise how to get rid of this error and abt coyote too
 
Misha Ver
Ranch Hand
Posts: 470
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is it a new installation of Tomcat? Did it work before? Will Tomcat start without deployed applications?
 
Santhosh Ganesan
Greenhorn
Posts: 2
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Yes its a new installation of tomcat.. Tomcat was started without deploying applications ..

The tomcat is started fine and after few minutes the Coyote is getting paused and stopped, and then while accessing the page , I am getting 503 error
 
Tim Holloway
Saloon Keeper
Pie
Posts: 17616
38
Android Eclipse IDE Linux
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A 503 error means that the application started and that a URL request was routed to it, but there was a failure in the application code.

In other words, the application has a bug in it. If you're not seeing a stack trace in that generally means that the application is also swallowing the exception instead of reporting it, but is apparently manually setting the response code to 503.

I've learned the hard way to NEVER simply silently consume an exception. Even the useless ones that people do on database connections:


If an exception was worth throwing, it's worth reporting, unless it's an application-style exception such as a "record not found: where the exception is not actually an error.
 
Consider Paul's rocket mass heater.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic