RuntimeException on InventoryApplicationLifeCycleEventListener Soon after Server Comes to RUNNING State
(Doc ID 2793947.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Communications Unified Inventory Management - Version 7.4.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Getting following error soon after after server comes to RUNNING state:
java.lang.RuntimeException
at oracle.communications.inventory.api.framework.logging.impl.FeedbackProviderImpl.getUserEnvironment(FeedbackProviderImpl.java:330)
at oracle.communications.inventory.api.framework.logging.impl.FeedbackProviderImpl.getFeedbackProvider(FeedbackProviderImpl.java:335)
at oracle.communications.inventory.api.framework.logging.impl.FeedbackProviderImpl.hasVisibleErrors(FeedbackProviderImpl.java:307)
at oracle.communications.inventory.api.framework.logging.impl.FeedbackLogImpl.error(FeedbackLogImpl.java:184)
at oracle.communications.inventory.api.framework.listener.InventoryApplicationLifeCycleEventListener.onRunning(InventoryApplicationLifeCycleEventListener.java:230)
at weblogic.t3.srvr.SrvrUtilities$1.run(SrvrUtilities.java:195)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
at oracle.communications.inventory.api.framework.logging.impl.FeedbackProviderImpl.getUserEnvironment(FeedbackProviderImpl.java:330)
at oracle.communications.inventory.api.framework.logging.impl.FeedbackProviderImpl.getFeedbackProvider(FeedbackProviderImpl.java:335)
at oracle.communications.inventory.api.framework.logging.impl.FeedbackProviderImpl.hasVisibleErrors(FeedbackProviderImpl.java:307)
at oracle.communications.inventory.api.framework.logging.impl.FeedbackLogImpl.error(FeedbackLogImpl.java:184)
at oracle.communications.inventory.api.framework.listener.InventoryApplicationLifeCycleEventListener.onRunning(InventoryApplicationLifeCycleEventListener.java:230)
at weblogic.t3.srvr.SrvrUtilities$1.run(SrvrUtilities.java:195)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
Analysis of InventoryApplicationLifeCycleEventListener class suggests error coming on setupTimers.
Debug logger on oracle.communications.inventory.api.framework.timer logged following additional statements confirming issue with timer setup:
[TimerFactory]: Is Standalone setup??
[TimerFactory]: Are Timers Already created??
[TimerFactory]: Throwing Validation Exception
[TimerFactory]: Are Timers Already created??
[TimerFactory]: Throwing Validation Exception
Changes
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 |
| References |