Missing Tomcat FrontEnd

Document ID : KB000031764
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms:

 

After start he application, under Agent logs we can see:

[ERROR] [IntroscopeAgent.Agent] Introscope AutoProbe will not run because the provided directives files are not valid: Invalid directives entry java${JVMCOMPATIBILITY}socket.pbd found in directives list file /opt/CA/wily/core/config/tomcat-typical.pbl Please restart with valid directives.

 

 

Environment:

Introscope: 9.7.0
Tomcat Application: 6.0.14
JavaSE 1.7.0.75.
JAVA Agent 9.1.5.

 

 

Cause:

 

Gist ${JVMCOMPATIBILITY} would get substituted at runtime with required JVM version to either map to java6socket.pbd or java7socket.pbd.
For some reason we are unable to calculate the runtime value so you can manually give pbd name in pbl or also you can try start the Agent with "java${JVMCOMPATIBILITY}socket.pbd" commented to make load "java6socket.pbd or java7socket.pbd".

 

 

Resolution/Workaround:

 

OPTION 1
1)Open your "tomcat-typical.pbl"
2)Add the PDB that match with your JVM being used as below:

#######################
# Directives Files
# ================
# One directives file name per line. Relative names
# are resolved against the location of this file.

java7socket.pbd (If you are using Java 7 into your application)
java6socket.pbd (If you are using Java 6 into your application)
toggles-typical.pbd
required.pbd
apm-common.pbd
java${JVMCOMPATIBILITY}socket.pbd
jvm.pbd
j2ee.pbd
java2.pbd
struts.pbd
taglibs.pbd
oraclejdbc.pbd
sqlagent.pbd


3)Restart the application to be monitored.

OPTION 2
1)Open your "tomcat-typical.pbl"
2)Comment the below PDB:


#java${JVMCOMPATIBILITY}socket.pbd


3)Restart the application to be monitored.

 

 

Additional Information:

 

-Please add just the PDB that match with your JVM being used.
-Please use Option 1 first and in case it not work use the option 2.