Web Workspace Locking Up with Error "AlarmsDataStore::populate:Operation failed with exception 'null'" (Doc ID 2038049.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Utilities Network Management System - Version 1.11.0.4 and later
Oracle Network Management for Utilities - DMS - Version 1.11.0.4 and later
Information in this document applies to any platform.

Symptoms

Web Workspace is Locking up.

Several operators reported that Web Workspace was locking up (hour-glassing) periodically for about 5 to 10 minutes at a time.
For most users, Web Workspace would simply become responsive again, and they could continue working.

One user, who was trying to load completed events, received the following error in a Windows dialog: AlarmsDataStore::populate:Operation failed with exception 'null'.

2015-07-21 11:29:30,127 [pool-2-thread-1] INFO com.splwg.oms.client.util.proxy.FaultToleranceContextFactory: Attempting to recover from a bad context
java.lang.reflect.UndeclaredThrowableException
  at $Proxy30.getTroubleCalls(Unknown Source)
  at com.splwg.oms.client.troubleinfo.PopulateCommand.execute(PopulateCommand.java:199)
  at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:339)
  at com.splwg.oms.jbot.adapter.JBotAdapter.runCommand(JBotAdapter.java:732)
  at com.splwg.oms.client.workagenda.ShowCallsCommand.execute(ShowCallsCommand.java:38)
  at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:339)
  at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:148)
  at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:261)
  at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:635)
  at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
  at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
  at java.util.concurrent.FutureTask.run(Unknown Source)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  at java.lang.Thread.run(Unknown Source)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 301 seconds
BEA1-0230A0FFD633CEA1B24E
  at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
  at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
  at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
  at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
  at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
  at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
  at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
2015-07-21 11:37:57,578 [Timer-0] ERROR com.splwg.oms.client.workagenda.AlarmsDataStore: execute command AlarmsDataStore::populate
java.lang.reflect.UndeclaredThrowableException
  at $Proxy0.getTroubleEventsNoCache(Unknown Source)
  at com.splwg.oms.client.workagenda.AlarmsDataStore$AlarmPopulationTask.run(AlarmsDataStore.java:1441)
  at java.util.TimerThread.mainLoop(Unknown Source)
  at java.util.TimerThread.run(Unknown Source)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-7FD8AC68D60CCEA1B24E
  at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
  at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)

Changes

 No patches or other changes have been made recently.

Cause

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