[
https://issues.jboss.org/browse/JBIDE-16520?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-16520.
---------------------------------
I don't get this error anymore (verified in JBDS 8.0.0.Alpha2 B70). I still can't
start a remote EAP 5.2 server though - JBIDE-16590
Remote EAP 5 fails to start - classToLaunch cannot be null
----------------------------------------------------------
Key: JBIDE-16520
URL:
https://issues.jboss.org/browse/JBIDE-16520
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Alpha2
Environment: JBDS 8.0.0.Alpha2 B41
Reporter: Martin Malina
Assignee: Rob Stryker
Labels: respin-a
Fix For: 4.2.0.Alpha2
Attachments: remote-eap5-error.png
Learning from Rob that JBIDE-16504 (Unable to start remote server - Unable to choose a
subsystem) only affected AS7/EAP6-like servers, I tried to test remote EAP 5.2.
Unfortunately, that doesn't work either.
When I added a remote EAP 5.2 and tried to start it, I got this error:
An internal error occurred during: "Starting JBoss EAP 5.x Runtime Server
marvin".
classToLaunch cannot be null
!remote-eap5-error.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira