[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1646) Provide direct feedback when server cannot be started because of security or other exceptions

[Rob Stryker (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. 

> Provide direct feedback when server cannot be started because of security or other exceptions
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-1646
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1646
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 2.0.0.GA
>         Environment: Eclipse3.3.1 (fall2 JEE Europa)  and JBossTools2.0.0.GA
> JBoss EAP 4.3.0
> jboss-as configuration: all, default, production
> Also tried this on JBossDeveloperStudio1.0.0 with same results
>            Reporter: Kapil Anand
>         Assigned To: Rob Stryker
>            Priority: Blocker
>             Fix For: 2.1
>
>
> 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

-- 
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