Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
Unable to instrument two standalone Jboss server - Nexus refused connection for reason is already in use"
Description
Two standalone instance JBOSS EAP 6.4 tried to start up file from different directories (e.g /app/jboss/node_01 and /app/jboss/node_02).
First instance was successfully integrated with foglight, but second one failed with Nexus error
Nexus refused connection for reason "Agent Name "pas-agent:JBoss:JBoss.config=:JBoss.home=/home/jboss/jboss-eap-6.4:JBoss.partition=:JBoss.server=standalone:hostname=myhostname" is already in use"
Cause
Both Jboss instances are giving 'standalone' as default jboss server name
Resolution
To resolve this, startup the Jboss standalone.sh with additional parameter -Djboss.server.name
Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.
Welcome to Quest Support
You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.
The Quest Software Portal no longer supports IE8, 9, & 10 and it is recommended to upgrade your browser to the latest version of Internet Explorer or Chrome.