Busy Cursor Gets Removed When It Should Not
(Doc ID 2229514.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Network Management for Utilities - DMS - Version 220.127.116.11 to 18.104.22.168.0 [Release 1.12 to 2.3]
Oracle Utilities Network Management System - Version 22.214.171.124 to 126.96.36.199.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.
The busy cursor seems to be removed when it should not be.
We have seen some instances where the busy cursor seems to get removed when it should not.
A user reported that their application became hung when they were trying to abort a FLISR plan that was running. They may have tried to abort multiple times because the busy cursor was removed.
I have seen the Stuck busy cursor at times when when the LDAP server has been slow. When entering a user and password, the busy cursor disappears after a short time, and then some time later the environment types get displayed in the login screen.
A user said they were creating an emergency plan from an event. The busy cursor disappeared and they selected the create button again. They ended up with 2 emergency plans that were related to the event.
2017-01-25 09:26:36,624 [Timer-0] WARN com.splwg.oms.jbot.JBotTool: Stuck busy curor. Resetting: 
2017-01-25 09:33:24,553 [Timer-0] WARN com.splwg.oms.jbot.JBotTool: Stuck busy curor. Resetting: [2, 0, 1]
2017-01-25 09:46:52,767 [pool-2-thread-6] WARN com.splwg.oms.client.util.proxy.ProxyInvocationHandler: invoke: SwmanService.doStepsStateTransition elapsed: 34896 ms. req: 83612 bytes, resp: 38078 bytes
Full thread dump Java HotSpot(TM) Client VM (24.79-b02 mixed mode):
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