Community
Participate
Working Groups
Created attachment 169582 [details] Debug log of jetty startup When attempting to start the server using following command line to the following, 'BindException: Address already in use' is being thrown. A full log with DEBUG set to true is attached. This happens on both Mac OS X and Ubuntu 10.4 operating system. java -jar start.jar etc/jetty.xml ############################################################### java.net.BindException: Address already in use at sun.nio.ch.Net.bind(Native Method) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) at org.eclipse.jetty.server.nio.SelectChannelConnector.open(SelectChannelConnector.java:208) at org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:288) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.Server.doStart(Server.java:237) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1018) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:983) 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.eclipse.jetty.start.Main.invokeMain(Main.java:447) at org.eclipse.jetty.start.Main.start(Main.java:605) at org.eclipse.jetty.start.Main.parseCommandLine(Main.java:238) at org.eclipse.jetty.start.Main.main(Main.java:77)
This is not a bug, but a change in the way that start.jar works. The contents of start.ini are always put on the command line, so because jetty.xml is in start.ini, you are getting it specified twice, hence 2 connectors and the already in use exception. If you want to run with additional xml's on the command line, you just need to specify the additional. If you want to replace the args from start.ini, you can specify a --ini= argument that will replace the ini with a null ini. So java -jar start.jar --ini= etc/jetty.xml works. I'll update the readme and then restage the releases.
This is a welcome change, but it has to be announced prominently in the release notice once the release is promoted in order to reduce possibility of someone tripping up on it. Also, this type of changes should be announced on the development list as soon as they are committed to eliminate extra cycles being spent by developers attempting to figure out what is going on. -Michael
Actually I believe we need to change the jetty.sh script as it puts the jetty.xml file on the runline by default. Jan
Re-assigning to Joakim to fix. Jan
The extra jetty.xml reference in jetty.sh has been removed.
