SEVERE: Error starting endpoint java.net.BindException: Cannot assign requested address:2217 at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:501) at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:515) at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:203) at org.apache.catalina.connector.Connector.start(Connector.java:1131) at org.apache.catalina.core.StandardService.start(StandardService.java:531) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) saying which address a bind was attempted for would accelerate the error resolution quite a bit!
This has been fixed in trunk and proposed for 6.0.x
This is fixed in 6.0.x and will be in 6.0.17 omwards.
this is particularly important, since e.g. today's debian stable kernel upgrade failed to re-deploy secondary network addresses from my /etc/network/interfaces file after re-boot. Only a manual sudo /etc/init.d/networking restart fixed this. Hard to detect unless tomcat tells you that despite you configuring 192.168.1.195 it tries to bind to 192.168.1.1 anyway... :(
see also Bug 46461