On 20/06/2016 20:58, Craig Lynch wrote:
> We run embedded tomcat on version 8, and for some reason are consistently
> seeing extreme slowness across all Tomcat endpoints at very consistent
> intervals of three hours. Once a site gets into the slow state, it is never
> able to recover, and stays unresponsive (requests take tens of minutes to
> hours) until the service is manually restarted.
> 
> There are no resource issues that I've been able to detect (heap seems
> fine, no apparent memory leaks, cpu is fine, network/db connections aren't
> exhausted, etc). Tomcat does seem to receive the requests, but for some
> reason does not seem to be processing them.
> 
> There is an exception that occurs right around the time the service goes
> into a bad state, which is the reason I believe this to be a Tomcat issue.
> The stack trace is as follows:
> 
> Exception in thread "mc-26" java.lang.IllegalMonitorStateException
>     at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(Unknown
> Source)
>     at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(Unknown
> Source)
>     at java.util.concurrent.locks.ReentrantLock.unlock(Unknown Source)
>     at java.util.concurrent.LinkedBlockingQueue.take(Unknown Source)
>     at org.apache.tomcat.util.threads.TaskQueue.take(TaskQueue.java:103)
>     at org.apache.tomcat.util.threads.TaskQueue.take(TaskQueue.java:31)
>     at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>     at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>     at java.lang.Thread.run(Unknown Source)

And when you Googled "IllegalMonitorStateException LinkedBlockingQueue"
what did you find?

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to