| Cause | Looking into the server.log and aveksaServer.log, it seems that there is a huge backlog of JMX transactions and the JBOSS server is attempting to replay the transactions during RSA Identity Governance & Lifecycle startup.
2017-12-01 01:49:41,635 WARN [com.workpoint.client.ClientContext] Attempt failed to retrieve authorization options from server. Either the server is not running or the client configuration may not be set up correctly. See the client log file for details.
2017-12-01 01:49:41,634 WARN [com.workpoint.client.ClientContext] Attempt failed to retrieve authorization options from server. Either the server is not running or the client configuration may not be set up correctly. See the client log file for details.
2017-12-01 01:49:41,635 INFO [STDOUT] 2017-12-01 01:49:41,635 [Timer-8] ERROR com.workpoint.queue.core.QMonitor - Attempt failed to create a client context. The monitors will not execute properly without this connection to the server.
java.rmi.RemoteException: Attempt failed to retrieve authorization options from server. Either the server is not running or the client configuration may not be set up correctly. See the client log file for details.
at com.workpoint.client.ClientContext.retrieveAuthInfo(Unknown Source)
at com.workpoint.client.ClientContext.open(Unknown Source)
at com.workpoint.client.ClientContext.open(Unknown Source)
at com.workpoint.queue.core.QMonitor.F(Unknown Source)
at com.workpoint.queue.core.QMonitor.I(Unknown Source)
at com.workpoint.queue.core.QMonitor.startMonitor(Unknown Source)
at com.workpoint.queue.WpQMonitors$_A.run(Unknown Source)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
|
on Dec 23, 2017