-
Title
Collecting foreign JMS metrics resulting in classnotfound -
Description
The following errors are filling up the java agent logs
2011-02-22 19:13:57.209 WARN [Periodic Discovery: WebLogic9] com.sitraka.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector - Unable to collect data for the MBean [com.bea:Name=StateNotificationTopicForeignDestination,Parent=[wliDomain]/JMSSystemResources[NA5530IntegrationJmsModule],Path=JMSResource[NA5530IntegrationJmsModule]/ForeignServers[NA5530ForeignServer]/ForeignDestinations[StateNotificationTopicForeignDestination],Type=weblogic.j2ee.descriptor.wl.ForeignDestinationBean] due to a temporary error condition; collection will be re-attempted at the next discovery interval
com.sitraka.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector$TemporarilyUnavailableMBeanException:
javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
at com.sitraka.pas.agent.plugin.periodic.jmx.WebLogic9MetricsCollector$WebLogic9RootNode.createMBeanInstanceNode(WebLogic9MetricsCollector.java:499)
at com.sitraka.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector$JmxRootNode.createMBeanNodes(AbstractJmxMetricsCollector.java:821)
at com.sitraka.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector$JmxRootNode.checkCreateMBeanNodes(AbstractJmxMetricsCollector.java:727)
at com.sitraka.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector$JmxRootNode.populate(AbstractJmxMetricsCollector.java:628)
at com.sitraka.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector$JmxPeriodicNodeTree.discoverTreeChanges(AbstractJmxMetricsCollector.java:1378)
at com.sitraka.pas.agent.periodic.PeriodicNodeTree.discovery(PeriodicNodeTree.java:463)
at com.sitraka.pas.agent.periodic.PeriodicNodeTree.access$400(PeriodicNodeTree.java:38)
at com.sitraka.pas.agent.periodic.PeriodicNodeTree$Dis -
Cause
The error is thrown when the agent attempts to collect metrics on their foreign jms destinations. It looks like their foreign jms are using jboss naming factory (the jnp classes)…And the agent fails while doing a lookup on org.jnp.interfaces.NamingContextFactory.
-
Resolution
Please check your classpath and add the jnp jar file (likely a jnp-client.jar) explicitly in the classpath while starting up the server. This would likely resolve the issue.
-
Additional Information
refer case:894328