UVMS does not stop normally and needs to be killed
Article ID: 87299
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message :
|ERROR| (N)io monitoring thread | com.orsyp.central.server.CentralServerAdapter | A request was rejected because UVMS main pool is full
java.util.concurrent.RejectedExecutionException: Task com.orsyp.central.server.CentralServerAdapter$1@3ccaedd5 rejected from java.util.concurrent.ThreadPoolExecutor@6eaa5b2a[Shutting down, pool size = 2, active threads = 2, queued tasks = 0, completed tasks = 14884551]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369)
at com.orsyp.central.server.CentralServerAdapter.onReadDataAvailable(CentralServerAdapter.java:260)
at com.orsyp.central.server.IOMonitoringPool.run(IOMonitoringPool.java:120)
at java.lang.Thread.run(Thread.java:745)
|ERROR| request-worker-10967 | com.orsyp.requestprocessor.UvmsRequestProcessor | Cannot send response to client! Invoke flush on output stream failed
java.nio.channels.ClosedChannelException
When a user attempts to stop the UVMS server via the command unistopms, the UVMS does not stop normally and errors similar to those above appear in the uvserver.log file.
If the UVMS runs on Windows, the associated service remains in a status of Stopping.
In order to restore the service, the associated Java process must be killed manually or wait for the 30 minutes timeout to take effect.
|ERROR| (N)io monitoring thread | com.orsyp.central.server.CentralServerAdapter | A request was rejected because UVMS main pool is full
java.util.concurrent.RejectedExecutionException: Task com.orsyp.central.server.CentralServerAdapter$1@3ccaedd5 rejected from java.util.concurrent.ThreadPoolExecutor@6eaa5b2a[Shutting down, pool size = 2, active threads = 2, queued tasks = 0, completed tasks = 14884551]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369)
at com.orsyp.central.server.CentralServerAdapter.onReadDataAvailable(CentralServerAdapter.java:260)
at com.orsyp.central.server.IOMonitoringPool.run(IOMonitoringPool.java:120)
at java.lang.Thread.run(Thread.java:745)
|ERROR| request-worker-10967 | com.orsyp.requestprocessor.UvmsRequestProcessor | Cannot send response to client! Invoke flush on output stream failed
java.nio.channels.ClosedChannelException
When a user attempts to stop the UVMS server via the command unistopms, the UVMS does not stop normally and errors similar to those above appear in the uvserver.log file.
If the UVMS runs on Windows, the associated service remains in a status of Stopping.
In order to restore the service, the associated Java process must be killed manually or wait for the 30 minutes timeout to take effect.
Environment
OS: All
OS Version: N/A
OS Version: N/A
Cause
Cause type:
Defect
Root Cause: The UVMS waits for all its threads to complete normally.
This can be an issue if the "Monitoring of Dollar Universe Nodes 5.x" service does not stop properly as it has a timeout of 30 minutes.
Defect
Root Cause: The UVMS waits for all its threads to complete normally.
This can be an issue if the "Monitoring of Dollar Universe Nodes 5.x" service does not stop properly as it has a timeout of 30 minutes.
Resolution
Update to a fix version listed below or a newer version if available.
The solution has reduced the timeout of v5 monitoring thread from 30 minutes to 2 minutes.
Fix Status: Released
Fix Version(s):
Component(s): Univiewer Management Server
Dollar Universe 6.8.21 - Available
The solution has reduced the timeout of v5 monitoring thread from 30 minutes to 2 minutes.
Fix Status: Released
Fix Version(s):
Component(s): Univiewer Management Server
Dollar Universe 6.8.21 - Available
Additional Information
Workaround :
Deactivate the Monitoring of v5 nodes (node settings / Option Services / Enable the Monitoring of Dollar Universe Nodes 5.x).
Deactivate the Monitoring of v5 nodes (node settings / Option Services / Enable the Monitoring of Dollar Universe Nodes 5.x).
Feedback
Yes
No
Powered by
