AnsweredAssumed Answered

Monitor Tibco Active Matrix ESB Service Grid

Question asked by WeiZ on Jun 10, 2011
Latest reply on Jun 12, 2012 by SMDawson
Hi, all

We are attempting to use Wily Introscope 9 to monitor Tibco Active Matrix ESB Service Grid 2.2. Service Grid is not an “app server” in the J2EE sense, but it is a java program, and it seems as a JVM it should be possible to monitor. Our problem is that after following the directions for installing the java agent, the node starts, but nothing seems to happen with Wily – no logs are even generated that would indicate the agent has started. Here are more details on what we’ve tried:

I followed the directions from Java Agent Guide, version 8.1. We are attempting to use JVM Autoprobe:

Run AutoProbe Connector for other application servers
To run the AutoProbe Connector, add the Agent.jar and the AutoProbe Connector
to the Application Server bootstrap classpath using this command:
-Xbootclasspath/p:wily/connectors/AutoProbeConnector.jar:PathToAgentJar

Attached is the Introscope.properties file.

Java version is:

java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_15-b04, mixed mode)

Platform is

Linux **** 2.6.9-100.ELsmp #1 SMP Tue Feb 1 12:04:42 EST 2011 x86_64 x86_64 x86_64 GNU/Linux


The AMX node uses a special launcher configuration file to execute the JVM. We have put the values needed into the bootclasspath, but nothing happens. Here’s the line we use from the .tra (config) file:

java.extended.properties=-Xbootclasspath/u01/app/admin/wily/javaagent/connectors/AutoProbeConnector.jar:/u01/app/admin/wily/javaagent/Agent.jar -XX:PermSize=128m -XX:MaxPermSize=256m -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Dcom.sun.management.jmxremote.port=9321 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

Attached IntroscopeAgent.profile

Sincerely,
Wei

Attachments

Outcomes