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

Rob Stryker (JIRA) jira-events at lists.jboss.org
Mon Apr 7 17:32:12 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBIDE-1646?page=all ]

Rob Stryker resolved JBIDE-1646.
--------------------------------

    Resolution: Done

I feel this issue is resolved. It was re-opened because Max could not get the dialog to appear when using bogus credentials. 

However, he was using bogus credentials on an unsecured server, and so the server was not rejecting his bogus credentials. 

> 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
>
>         Attachments: JBIDE-1646.jpg
>
>
> 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

        



More information about the jbosstools-issues mailing list