[ http://jira.jboss.com/jira/browse/JBIDE-1646?page=all ] Kapil Anand updated JBIDE-1646: ------------------------------- Description: I am able to launch JBoss 4.3.0 from command line using run.sh/run.bat, but it fails to start from within eclipse. Java process just abruptly dies while starting up . Logs do not show any error or exception, neither anything shows up on stderr eclipse is capturing and I could not establish any pattern in this since I tried this multiple times and the process died at different points. Create a new JBoss 4.2 Runtime, but use the JBoss-AS budled with JBoss EAP 4.3.0 Create a new jboss instance using any one of the configurations: all, default, production Start the jboss instance. Instance will fail to start without any apparent reasons. The same instance can be launched successfully from command line using run.sh -c production was: I am able to launch JBoss 4.3.0 from command line using run.sh/run.bat, but it fails to start from within eclipse. Java process just abruptly dies while starting up . Logs do not show any error or exception, neither anything shows up on stderr eclipse is capturing and I could not establish any pattern in this since I tried this multiple times and the process died at different points. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1646?page=all ] Max Andersen updated JBIDE-1646: -------------------------------- Fix Version/s: 2.1 Priority: Blocker (was: Major) Very little information to go on but needs to atleast verify JBoss 4.3 works fine with us. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1646?page=all ] Max Andersen updated JBIDE-1646: -------------------------------- Summary: Provide direct feedback when server cannot be started because of security or other exceptions (was: Unable to start JBoss EAP 4.3.0) agreed and thanks for the feedback - fortunately there were a reasonable explanation behind it ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1646?page=comments#action_12400244 ] Rob Stryker commented on JBIDE-1646: ------------------------------------ I've sent an email to Tim DeBoer (eclipse, ibm, server tools) asking if there's any way to customize the timeout / error dialog. Right now it doesn't seem like there is, and so we'll have to deal with that dialog being vague for now. Hopefully I can have an effect on the 3.0 stream if I make it a hot-bug. I've not committed to bugzilla until I get a response from him. As for direct response, for now the way to get feedback into what failed is in the JBoss Servers View, expanding the Event Log. It will tell you the causes of the errors, when the server is forcefully shut down, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1646?page=all ] Rob Stryker resolved JBIDE-1646. -------------------------------- Resolution: Done svn-fixed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1646?page=comments#action_12407194 ] Rob Stryker commented on JBIDE-1646: ------------------------------------ I am experiencing the following. When the sever is not secured and you use bogus username / password: During startup, the poller is setting the credentials, and executing the jmx to poll the server. The server itself is allowing these credentials to go through because the JMX is not secured. Therefore it's ignoring the credentials that have been set. This would be an upstream bug or perhaps its a feature. I'm not sure. During shutdown, I am not experiencing a hang. I am experiencing a clean shutdown. When the server *is* secured and you use an incorrect username / password: During startup: The server begins its startup phase... The event log shows JMX is unreachable The event log shwos JMX is not bound yet A dialog comes up when JMX responds "no, those credentials are incorrect". The user can provide new credentials (which would then be saved to the workspace server object) Or... The user can cancel, terminating the startup. The reason invalid credentials are accepted when the rmi adapter is not secured is because the security interceptor is never even reached, and so there's nothing even validating whether credentials were set at all. Therefore, if its not secured, any username and any password will work just fine. No one's checking. Attachment provided. I may change the text now that I've reviewed whats written there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1646?page=comments#action_12407198 ] Rob Stryker commented on JBIDE-1646: ------------------------------------ As for stop "freezing", there are a number of bugs regarding incorrect state status in wtp 2.0.1, and with WTP's server state threads freezing. They claim to be fixed in 3.0 but I'll be sure to check for that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira