Bug#572048: I can confirm failure to start

[Pier Luigi Pau]

Hello,

I couldn't get tomcat6 6.0.24-2 to start, either, and so far I haven't
found anything better to do than revert to a previous version
(6.0.20-dfsg1-1). This is on amd64, for the record.

Purging the packages and reinstalling 6.0.24-2 didn't help; nor did
switching between openjdk-6 and sun-java6.

I had lines similar to these in my /var/log/tomcat6/catalina.(date).log:

><<<<
1-mar-2010 10.34.37 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/lib/jvm/java-6-openjdk/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/jni:/lib:/usr/lib
1-mar-2010 10.34.37 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
1-mar-2010 10.34.37 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 570 ms
1-mar-2010 10.34.37 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
1-mar-2010 10.34.37 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.24
1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ROOT.xml
1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor docs.xml
1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor examples.xml
1-mar-2010 10.34.38 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
1-mar-2010 10.34.38 org.apache.catalina.startup.Catalina start
INFO: Server startup in 591 ms
1-mar-2010 10.34.38 org.apache.catalina.core.StandardServer await
GRAVE: StandardServer.await: create[8005]:
java.net.SocketException: Invalid argument
	at java.net.PlainSocketImpl.socketBind(Native Method)
	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
	at java.net.ServerSocket.bind(ServerSocket.java:336)
	at java.net.ServerSocket.<init>(ServerSocket.java:202)
	at org.apache.catalina.core.StandardServer.await(StandardServer.java:373)
	at org.apache.catalina.startup.Catalina.await(Catalina.java:657)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:617)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
><<<<

An interesting behaviour I noticed: running /etc/init.d/tomcat6 start
manually gave me an indication of failure; instead, if I rebooted my
box altogether, it apparently worked, and I had a file with a process
id at /var/run/tomcat6.pid, but by the time I could get into a shell,
the process had somehow disappeared (died?). /etc/init.d/tomcat6 stop
would answer that tomcat6 wasn't running, /etc/init.d/tomcat6 start
would complain that there was a pid file and therefore nothing had to
be done.

Regards,
Pier Luigi Pau