geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Hogstrom (JIRA)" <>
Subject [jira] Closed: (GERONIMO-1226) Remove broken Reboot option from Console Shutdown/Restart
Date Wed, 23 Nov 2005 16:56:37 GMT
     [ ]
Matt Hogstrom closed GERONIMO-1226:

    Resolution: Fixed

Hogstrom:~/dev/geronimo/applications hogstrom$ svn commit -m "GERONIMO-1226 Remove shutdown
option from console" 
Sending        applications/console-framework/src/webapp/WEB-INF/data/pageregistry.xml
Sending        applications/console-standard/src/webapp/WEB-INF/view/servermanager/help.jsp
Sending        applications/console-standard/src/webapp/WEB-INF/view/servermanager/normal.jsp
Sending        applications/console-standard/src/webapp/WEB-INF/view/servermanager/shutdown.jsp
Transmitting file data ....
Committed revision 348486.

> Remove broken Reboot option from Console Shutdown/Restart
> ---------------------------------------------------------
>          Key: GERONIMO-1226
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: console
>     Versions: 1.0
>  Environment: windows xp pro
>     Reporter: Joe Bohn
>     Assignee: Matt Hogstrom
>      Fix For: 1.0
>  Attachments: shutdown.patch
> The "Reboot" option on the Web Console is not functional in it's current implementation.
  I posted a question on this to dev  (see thread:
).  The response was that I should remove this capability for now. 
> Here are the problems based upon the configuration:
> The failures from the reboot vary according to the configuration.  I've 
> only tried this with the default configuration, jetty only, and tomcat 
> only ... but this is the results:
> Jetty only
>   - Gets an error while starting G-Bean 
> "geronimo:type=NetworkService,name=EJB" and indicates it is in the 
> failed state.  This was Caused by: Address 
> already in use: JVM_Bind.  In the error log it looks like the port was 
> 4201.  However, the things (at least for the console) appear to work 
> normally after the restart.
> Tomcat only
>   - Doesn't get any errors, but results in the JVM terminating without 
> an attempt at restart.  I haven't tracked down yet who is doing the 
> system exit but there isn't much in the log to indicate a failure.
> Both Jetty & Tomcat (Jetty on 8080, Tomcat on 8090)
> - Gets a whole bunch of error on restart - starting with the same error 
> as Jetty only above plus numerous errors from Tomcat in BaseModelMBean, 
> Registry, Connector, JkMain.  However, once again the console appears to 
> function appropriately (of course it is running on Jetty).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message