Troubleshooting
Problem
JBoss 4.3 JMS: Agent Server on start up throws InvocationTargetException - cannot find class org/jnp/server/NamingBean.
Symptom
After configuring JBoss JMS 4.3 with the v8.5
InvocationTargetException error thrown, caused by ClassNotFound
exception for the class org/jnp/server/NamingBean.
Resolving The Problem
To use JBoss JMS with v8.5 of the Sterling application, the
customer must add a few jar files to the CLASSPATH. Section 13.3.1.3 of v8.5
Installation Guide states the following jar files:
** javassist.jar
** jbossall-client.jar
** jboss-aop-jdk50-client.jar
** jboss-aop-jdk50.jar
** jboss-messaging-client.jar
** log4j.jar
** trove.jar
** jbossall-client.jar
** jboss-aop-jdk50-client.jar
** jboss-aop-jdk50.jar
** jboss-messaging-client.jar
** log4j.jar
** trove.jar
In addition, the customer should also
include the jnpserver.jar in the CLASSPATH. This file is present under
<JBOSS_HOME>/server/<server_name>/lib folder. This file contains the
org/jnp/server/NamingBean.class and one can install this jar to the
AGENTDynamicclasspath.cfg through install3rdParty utility.
If the Agent Server on start up throws
javax.naming.NameNotFoundException, refer to the article NFX8493 for a possible
resolution.
[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Historical Number
NFX8576
Product Synonym
[<p><b>]Escalation ID[</b><p>];136869;[<p><b>]Severity[</b><p>];Normal
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21552553