Unable To Register Two AD4J Agents Deployed In Tomcat Instances On Same Machine
(Doc ID 762582.1)
Last updated on OCTOBER 19, 2018
Applies to:Enterprise Manager Grid Control - Version: 10.2.0.4
This problem can occur on any platform.
-- Problem Statement:
Unable to register two AD4J agents deployed in tomcat instances in the same server.
Upon start the first ad4j agent gets registered OK with the ad4j console, but the second fails while starting with the messages:
JAM Agent: Initialization Code 0, 0x3201b920 : Normal
JAM Agent: Build number 3514
JAM Agent: webserver is Tomcat
JamAgent S-DIAGNOSTIC Code : Thread 0xd6dd80, class com.trema.acm.core.storedbalances.BalanceUpdaterManagerImpl
JAM Agent Tomcat.main does not contain org.apache.catalina.core.StandardEngine
JAM Agent : Tomcat Port not Found in max retries
JAM Agent Tomcat.httpProcessor does not contain org.apache.tomcat.util.net.PoolTcpEndpoint
JVM VENDOR=Sun Microsystems Inc., VERSION=1.5.0_14, OSNAME=SunOS-5.10, CPU ARCHITECTURE=64 bit
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|