How to address the java agent of an AD4J 10.2.0.4 install registering a port of 5555 when running in App Server 10.1.2.x (Doc ID 577267.1)

Last updated on APRIL 22, 2013

Applies to:

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

Goal

This note provides source code and compiled classes for a servlet named SetLoggingJVMUniqueIdServlet, that can be used in conjunction with the "java agent" present in version 10.2.0.4 of the Oracle Application Diagnostics For Java (AD4J) product.

By following the directions in this note, the SetLoggingJVMUniqueIdServlet can be configured to run before the "jamagent" servlet and control the value of a System property (named logging.jvm.unique.id) that is used to influence the port value that the agent will use to identify itself when it registers with the central AD4J Console.

This allows a distinct "port" value to be used in cases where AD4J is unable to correctly identify a unique "port" value for J2EE container environments like Oracle Containers for J2EE, BEA WebLogic or IBM WebSphere.

Solution

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