OSM Cluster: Error: Failed to Retrieve JMS Redelivery Configuration Due to Null Exception
Last updated on SEPTEMBER 26, 2017
Applies to:Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.
On : 7.2.4 version
1. Today during the scheduled automatic restart of OSM and other OCS stack applications, Node 2 server threw errors during startup. OSM did come up. However orders got stuck at a particular automation task.
The customer is running OSM 220.127.116.11.9 on the cluster and consistently getting following error during the restart of the cluster
<05:32:30> <Error> <oms> <ocsosmapp001> <osm7prod_ms1> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'>
<0000LgPbcY00joIpqoDCiY1Oqsnf000002> <1490783550841> <BEA-000000>
<helper.JMSHelper: Failed to retrieve JMS redelivery configuration due to
null com.mslv.oms.OMSException at
com.mslv.oms.j2ee.J2EEServiceWebLogic.getJMSRedeliveryConfiguration(J2EEServiceWebLogic.java:1185) at com.mslv.oms.view.rule.helper.JMSHelper$1.
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