[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1646) Unable to start JBoss EAP 4.3.0

[Kapil Anand (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1646?page=comments#action_12396869 ] 
            
Kapil Anand commented on JBIDE-1646:
------------------------------------

I am sorry, I forgot to update this though I add comments in the Forum thread.
It worked fine after I made the suggested changes in the configuration.

There was no real issue, just that the JMX invokers were pre-configured to be secured and I had been using them without that option previously.
So the Eclipse plugin was not able to query the status of the Jboss server and was killing the launched javaw process itself. This became evident when the Startup Events were analyzed.

One enhancement could be that the plugin could report the possible reasons of failure in the dialog that pops up.


> Unable to start JBoss EAP 4.3.0
> -------------------------------
>
>                 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
>            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