JMS Unit Of Work Issue In OSM 7.3.0.0.0 (Doc ID 2195256.1)

Last updated on OCTOBER 25, 2016

Applies to:

Oracle Communications Order and Service Management - Version 7.3.0.0.0 to 7.3.0.0.0 [Release 7.3.0]
Information in this document applies to any platform.

Symptoms

On : OSM 7.3.0.0.0 version,

ERROR
-----------------------
The issue was viewed in the logs


Caused By: java.lang.NoClassDefFoundError: Could not initialize class oracle.communications.ordermanagement.automation.plugin.AutomationPluginDeployment
  at com.mslv.oms.automation.AutomationDispatcher.isOSMUnitOfOrder(AutomationDispatcher.java:958)
  at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.hasOSMUnitOfOrder(ClusterMessageHandlerBean.java:403)
  at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.continueProcessMessageNormally(ClusterMessageHandlerBean.java:214)
  at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(ClusterMessageHandlerBean.java:108)
  at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:451)
  Truncated. see log file for complete stacktrace




BUSINESS IMPACT
-----------------------

while consuming the messages from TOM to SOM errors are popping up and orders not moving

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms