We instrumented an E-Business Oracle 9iAS app server with an X-agent.The system is configured to start 2 JVMs per app server for performance reasons. However both these app servers use the same jserv.properties file, which is where the java start up parameters are defined. We therefore get duplicate agents started as the agent name is defined by this setting in the file:
wrapper.bin.parameters=-Dquest.agent.appserverinfo=oesval_vhc-01:Generic:1.1.2:ebusiness-val
The multiple number of jvms per appserver is something seen only on OracleAS and so our Oracle specific agents takes into account this set up and forms agent names automatically. But since , you are using the X-agent which is a generic agent for all JVMs in general, automatic handling of multiple jvms doesn't happen. That is why you see the agent name conflict.
For 5.6.1, This is a limitation with the X-agent in the sense, its written for JVMs in general, and to handle multiple-jvms inside one appserver is a "OracleAS special" thing...which our OracleAS dedicated agent supports.
An enhancement request JEE-6209 has been filed for the ability for X-Agent to handle multiple Oracle 9iAS processes
STATUS:Fixed in 5.7.x and later versions
For 5.7.x and above:
Add the below parameter to jserv.properties file
wrapper.bin.parameters=-Dquest.agent.appserverinfo.systemname.append=_jvm{applicationarguments.-opmindex}
