[ http://wso2.org/jira/browse/MASHUP-426?page=comments#action_14024 ] Channa Gunawardena commented on MASHUP-426: -------------------------------------------
This can happen if there is some issue with the buid that prevents the server from starting up normally. The issue is apparent when starting up using the command line, but when wrapped, the service wrapper startus up and both the windows service manager and the monitor believe the server has also started up at this point. One possibility is to have a WSO2 component notify the monitor of a successful startup (or errors), so that status indication can be based on our code starting up, rather than feedback from the wrapper. > Admin console unavailable > ------------------------- > > Key: MASHUP-426 > URL: http://wso2.org/jira/browse/MASHUP-426 > Project: WSO2 Mashup Server > Issue Type: Bug > Environment: Vista, 11/30 nightly build from keith > Reporter: Jonathan Marsh > Assigned To: Channa Gunawardena > > Downloaded and ran the installer. Everything appeared fine. Firewall asked > for an exception, which I granted. > Tray icon active, reports service started, but selecting the admin console > link brings back a blank page. Other URLs in 7443 or 7762 also blank. > Windows Services monitor shows the Mashup service running. Windows Event > Viewer doesn't turn up anything other than "The WSO2 Mashup Server service > entered the running state." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
