[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_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. 

> 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