Port conflicts don't cause a shutdown. You will get an error message on
the console and in the log like the following:
09:08:35,375 ERROR [GBeanInstanceState] Error while starting; GBean is
now in the FAILED state: objectName="geronimo.server:J2EEAppl
ication=null,J2EEModule=org/apache/geronimo/Jetty,J2EEServer=geronimo,j2eeType=GBean,name=JettyWebConnector"
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
at java.net.ServerSocket.bind(ServerSocket.java:318)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at
org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:391)
at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:477)
at
org.apache.geronimo.jetty.connector.JettyConnector.doStart(JettyConnector.java:203)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:936)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325)
<SNIP>
John
Aaron Mulder wrote:
Have we checked what happens with port conflicts recently? It would
be ideal if that didn't cause a shutdown, so you could go into the
console and resolve the conflict (so long as *all* the web ports don't
conflict). I'm trying to remember what else I've run into that caused
a shutdown... If the config.xml has a bogus entry, that causes a
shutdown, and I didn't like that much either.
What are the problems we expect to see that we think *should* cause a shutdown?
Aaron
On 11/30/05, David Jencks <[EMAIL PROTECTED]> wrote:
On Nov 30, 2005, at 4:56 AM, John Sisson wrote:
This one is probably for Aaron..
I am looking at the Daemon.doStartup() code and noticed that it
doesn't call the loadFailed and startFailed methods of the
StartupMonitor interface (used by the ProgressBarStartupMonitor and
the StaticStartupMonitor I am working on).
Currently the doStartup() code calls loadGBeans() and start(), and
they can throw InvalidConfigException. If that happens, the server is
shut down.
Should we try to limp on if that happens and pass the exception to the
loadFailed or startFailed methods of the StartupMonitor interface or
is there a good reason why we shut down the server under these
circumstances?
I think shutting down is the most appropriate action at that point.
thanks
david jencks
John
