Mark,
I was also concerned w/ the version of Java they are using. See my other
note. Thanks again for the help. I'll get back to you if I have more.
-Andrew
On Tue, Nov 27, 2018 at 1:44 PM Mark Thomas wrote:
> On 27/11/2018 18:24, Andrew Carr wrote:
> > Tomcat 8.5.24
> > Java - (1.8.0-zing_
Mark,
Thanks for the other advice. I have recommended upgrading as a possible
solution. I do see the inconsistencies you are referring to, and I will
try to generate a thread dump with the issue happening using a different
tool, but the issue is intermittent. Thank you much for the help, I'll m
On 27/11/2018 18:24, Andrew Carr wrote:
> Tomcat 8.5.24
> Java - (1.8.0-zing_16.12.3.0-b2-product-azlinuxM-X86_64 mixed mode [Mon Aug
> 13 05:18:16 PM UTC 2018]):
One for your JVM vendor at this stage I think.
If you (or they) can show a deadlock and include information on what is
holding the loc
Tomcat 8.5.24
Java - (1.8.0-zing_16.12.3.0-b2-product-azlinuxM-X86_64 mixed mode [Mon Aug
13 05:18:16 PM UTC 2018]):
On Wed, Nov 21, 2018 at 6:49 AM Mark Thomas wrote:
> And which version of Java?
>
> See also comments below.
>
> On 20/11/2018 22:16, Mark Thomas wrote:
> > Which version of Tomca
And which version of Java?
See also comments below.
On 20/11/2018 22:16, Mark Thomas wrote:
> Which version of Tomcat are you using?
>
> Mark
>
>
> On 20/11/2018 21:02, Andrew Carr wrote:
>> Wait, I think I might see what I did, let me try again.
>>
>> Found one Java-level deadlock:
>> ===
Which version of Tomcat are you using?
Mark
On 20/11/2018 21:02, Andrew Carr wrote:
Wait, I think I might see what I did, let me try again.
Found one Java-level deadlock:
=
"Thread-96":
waiting to lock monitor 0x3a0d6938 (object 0x80048462700, a
java.util.concur
Wait, I think I might see what I did, let me try again.
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 mon
Do you mean because the thread that is deadlocked is the
QuartzSchedulerThread?
The classloader and the concurrent thread are both waiting on Quartz.
Quartz thread is defined below: (Other than that I do not know what you
mean when you say it is not consistent.) Should I provide the full dump in
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 11/20/18 12:50, Mark Thomas 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
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
12 matches
Mail list logo
