Error In Data Source Creation While Performing An OSM Installation In A Cluster Environment.

(Doc ID 2220883.1)

Last updated on AUGUST 21, 2017

Applies to:

Oracle Communications Order and Service Management - Version and later
Information in this document applies to any platform.


After installation of OSM  without a built-in Proxy Server and restarting the managed servers, the customer received the following JDBC DataSource errors


com.mslv.oms.dataaccesslayer.ProxyException: java.lang.ExceptionInInitializerErrorNested Exception: java.lang.ExceptionInInitializerErrorNested Exception: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
at com.mslv.oms.dataaccesslayer.AbstractProxy.execute(
at com.mslv.oms.poller.RuleEngineChecking.dbOperation(
at com.mslv.oms.poller.RuleEngineChecking.init(
at javax.servlet.GenericServlet.init(
at weblogic.servlet.internal.StubSecurityHelper$
at weblogic.servlet.internal.StubSecurityHelper$

The issue can be reproduced at will with the following steps:
1. Install OSM in cluster  without built-in WebLogic Proxy Server.

The issue has the following business impact:
Due to this issue, users cannot run OSM


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