[
https://issues.jboss.org/browse/JBIDE-16520?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-16520:
-------------------------------------
I suspect this is a duplicate of
https://issues.jboss.org/browse/JBIDE-16532.
If you got this result after testing several servers, then the issue is that the launch
configuration was caching data it shouldn't be caching. It was doing this under the
assumption that the launch objects were different, but they were in fact the same object,
so state should not be kept.
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
Fix For: 4.2.0.Beta1
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