AD4J java agent incorrectly registers as port 5555 when running under OC4J 10.1.2.x

(Doc ID 564329.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Enterprise Manager Base Platform - Version and later
Information in this document applies to any platform.
***Checked for relevance on 22-Mar-2013***


You have deployed the java agent of an AD4J Release 1 (Build 2807) to an OC4J instance running within an Application Server 10.1.2.x installation. However, the PORT that the AD4J agent dynamically discovers and registers with the AD4J console has an unexpected value. The AD4J agent registers with the default port value of 5555 rather than the AJP port that OPMN has dynamically assigned to that instance.

This causes issues if AD4J is to be used in conjunction with multiple OC4J instances, since each JVM in this scenario is always registered with the same 5555 value and causes a conflict at the JAM Console, where only one JVM can be seen.

In the case of multiple AD4J java agents running in different AD4J instances, this problem can be overcome by manually assigning distinct id's after the agent's deployment, which can be achieved by editing the web.xml file for the deployed AD4J agent and adding a jamjvmid servlet parameter, as shown below:


        <description>Jam console host -</description>
        <description>Jam console port</description>
        <description>Seconds to wait before retrying connection to disconnected console</description>
        <description>Timeout in seconds for long operations</description>
        <description>Jam log level</description>
        <description>Max backed off time to wait for GC to finish</description>
        <description>Default directory for extracting native libraries</description>
        <description>Keep alive timeout in seconds for agent to re-connect to the console</description>
        <param-value>SOME UNIQUE VALUE</param-value>
        <description>Unique Identifier for JVM.</description>


However, this is of specific impact if you plan to run multiple instances of the same OC4J process via
OPMN's "numproc" setting, in which case the same web.xml file will be used by all instances of the same OC4J instance (and therefore the jamjvmid will not be unique between those instances).

In the event that the opmn.xml configuration for any OC4J instance where the agent has been deployed also has numprocs > 1, all AD4J agents will register using the default 5555 value for the javajvmid parameter and it is not be possible to see, interact with or analyze more than one of these instances via the AD4J console.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms