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
[email protected] rejected from
[email protected][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.