Cannot start Tomcat 6.0.26 after upgrading to Debian Squeeze

Question

The working setup of Tomcat stopped working after dist-upgrade on Debian (for compression). 8005 is the shutdown port, but it is not busy. Any ideas on what this could be? This is not exactly a self-speaking exception. This is a magazine from catalina:

org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[8005]:                          
java.net.SocketException: Invalid argument                                      
        at java.net.PlainSocketImpl.socketBind(Native Method)        
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at org.apache.catalina.core.StandardServer.await(StandardServer.java:373)
        at org.apache.catalina.startup.Catalina.await(Catalina.java:662)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:614)
        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:289)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Answer 1

The problem is resolved, it is connected with some IPv6 materials, so to skip this, you need to add the -Djava.net.preferIPv4Stack = true parameter to the JAVA_OPTS variable in the catalina.sh script file or change the kernel configuration. More about this:

http://confluence.atlassian.com/pages/viewpage.action?pageId=214863647

Answer 2

, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572048

:   echo 0 > /proc/sys/net/ipv6/bindv6only : /etc/sysctl.d/bindv6only.conf