A ClassNotFound Exception is thrown while running start-admin-probe.sh .
Article ID: KB0092427
Updated On:
| Products | Versions |
|---|---|
| TIBCO Service Performance Manager | - |
| Not Applicable | - |
Description
Description:
While running start-admin-probe.sh, you may see a NoClassDefFoundError Exception. This is caused due to missing JARs when you install the BW plugin-in in a separate home directory which is not the <SPM_Home> directory. Here is a list of missing JARs from SPMBW agent:
slf4j-api-1.5.2.jar
slf4j-log4j12-1.5.2.jar
tibcrypt.jar
log4j-1.2.15.jar
Symptoms:
When executing start-admin-probe.sh, the following exception is thrown given:
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/log4j/Priorty
at com.tibco.rta.log.impl.DefaultLogManager.getLogger(DefaultLogManager.jva:43)
at com.tibco.rta.probe.bw.admin.BWAdminProbe.<clinit>(BWAdminProbe.java:3)
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Priority
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 2 more
Cause:
When the BW plug-in is installed in a separate directory other than <SPM_Home>, the SMBW agent will not have the following JARs that comes with SPM engine installation:
slf4j-api-1.5.2.jar
slf4j-log4j12-1.5.2.jar
tibcrypt.jar
log4j-1.2.15.jar
Resolution
As a workaround, modify the classpath in start-admin-probe.sh (or .bat) or copy the missing JARs from the SPM lib folder to <tibco home>/spm/2.2/smbw-agent/lib/ext .
Issue/Introduction
A ClassNotFound Exception is thrown while running start-admin-probe.sh .
Additional Information
This issue was tracked under Change Request SPM-5969, which has been addressed in the latest release, SPM 2.3.0 .
Feedback
Yes
No
Powered by
