"WLEventContextImpl cannot be cast to javax.sql.DataSource" Error when Deploying Application
(Doc ID 2299698.1)
Last updated on AUGUST 06, 2022
Applies to:
Oracle Utilities Network Management System - Version 1.12.0.3 and laterOracle Network Management for Utilities - DMS - Version 1.12.0.3 and later
Information in this document applies to any platform.
Symptoms
In upgrade of production from 1.12.0.2 to 1.12.0.3 an error occurs when deploying application.
I've upgraded production from 1.12.0.2 to 1.12.0.3. When I try to activate changes I get the following:
weblogic.jndi.internal.WLEventContextImpl cannot be cast to javax.sql.DataSource
ERROR
weblogic.application.ModuleException: java.lang.ClassCastException: weblogic.jndi.internal.WLEventContextImpl cannot be cast to javax.sql.DataSource
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:192)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:187)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
at weblogic.work.ContextWrap.run(ContextWrap.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
Changes
This occurred during a upgrade from 1.12.0.2 to 1.12.0.3
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |