Error Getting While Upgrading The ORMB Application From 25030 To 2.8
(Doc ID 2662779.1)
Last updated on DECEMBER 13, 2023
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.5.0.3.0 and laterInformation in this document applies to any platform.
Goal
Why are we receiving the following errors?
weblogic.application.ModuleException: javax.naming.NameNotFoundException: While trying to lookup 'ouaf.servicebean' didn't find subcontext 'ouaf'. Resolved ''; remaining name 'ouaf/servicebean'
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
Truncated. see log file for complete stacktrace
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'ouaf.servicebean' didn't find subcontext 'ouaf'. Resolved ''; remaining name 'ouaf/servicebean'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:227)
at weblogic.
Solution
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
| Goal |
| Solution |
| References |