The thread dump you posted doesn't seem to be consistent with the summary you provide below. Specifically for the "Event Manager Thread_QuartzSchedulerThread". Might there be multiple threads with that name and we are looking at the wrong one?

Mark


On 20/11/2018 19:06, Andrew Carr wrote:
My apologies, that is the offending thread, see below: (Should I open a
ticket to attach full dumps?)

Found one Java-level deadlock:
=============================
"Thread-96":
   waiting to lock monitor 0x3a0d6938 (object 0x80048462700, a
java.util.concurrent.ConcurrentHashMap),
   which is held by "Thread-29"
"Thread-29":
   waiting to lock monitor 0x3a0d58b0 (object 0x1000bbc1dd20, a
java.lang.Object),
   which is held by "Event Manager Thread_QuartzSchedulerThread"
"Event Manager Thread_QuartzSchedulerThread":
   waiting to lock monitor 0x3803a2c0 (object 0x800674b7830, a
org.apache.catalina.loader.ParallelWebappClassLoader),
   which is held by "Thread-29"


On Tue, Nov 20, 2018 at 12:50 PM Mark Thomas <ma...@apache.org> wrote:

On 20/11/2018 15:21, Andrew Carr wrote:
Hello,

We have been seeing some intermittent issues with the parallel
classloader.  I do not want to jump to any conclusions and say this is a
bug w/ the classloader, but we are getting deadlocked threads, pretty
randomly, when launching the server.  I was wondering if anyone had
experienced this issue or if you could review the attached thread dump
and
give me some feedback.

There is no associated log file for the time the deadlock was occurring,
I
am working on getting that.  In unrelated log files I saw some
concurrency
exceptions, non-thread safe access to lists basically.  I believe that
issue has been corrected in the source code, and I am not sure the
concurrency exception has anything to do with the deadlock occurring
during
classloading.

Personally I am of the belief that unsafe maps / lists could possibly
cause
the classloader to deadlock.

I can put the full dumps in a ticket, I just hate to open another
classloader ticket.

I don't see a deadlock in the provided stack trace.

Mark

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




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

Reply via email to