Unable to start EAP 4.3 through JON 2.2
Issue
- The JON Server, JON Agent, and EAP 4.3 instance have been installed on the same RHEL 64-bit VM. The JON Server and JON Agent started successfully and was able to initially import the EAP instance and deploy the initial version of the application. The application was shown as being deployed successfully but could not be accessed via browser. Determined the EAP instance needed to be bound to the IP address of the VM. Stopped the EAP instance through JON, made the configuration change for the binding IP address, and restarted the EAP instance. When clicking the 'failure' link for the start operation, the following exception was thrown:
-
at org.rhq.plugins.jbossas.JBossASServerOperationsDelegate.start(JBossASServerOperationsDelegate.java:211) at org.rhq.plugins.jbossas.JBossASServerOperationsDelegate.invoke(JBossASServerOperationsDelegate.java:120) at org.rhq.plugins.jbossas.JBossASServerComponent.invokeOperation(JBossASServerComponent.java:343) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:484) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
-
Environment
- JBoss Operations Network(JON) 2.2
- JBoss Enterprise Application Platform(EAP) 4.3
- Red Hat Enterprise Linux (RHEL) 5 64-bit
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.