If you know what the cause is please add that information to the Jira issue.
I’d really like to understand what is causing this.
Ralph
> On Jul 6, 2016, at 7:06 AM, Leon Finker wrote:
>
> Based on google searches, it turns out to be a classic class loading
> deadlock. I
Leon, I would like to see this myself. Is it possible to attach the full thread
dump or create a Jira ticket with the full thread dump?
Sent from my iPhone
> On 2016/07/06, at 23:06, Leon Finker wrote:
>
> Based on google searches, it turns out to be a classic class loading
Based on google searches, it turns out to be a classic class loading deadlock.
I found one thread that was inside the class' static initializer: ,
which then eventually ended up logging indirectly and getting blocked on:
at
The StackOverflow link may still be relevant if the problem is caused by class
loading (by different classloaders?) from different threads.
Leon, is there any other thread in the thread dump that is loading a class?
Sent from my iPhone
> On 2016/07/06, at 6:31, Ralph Goers
The stack overflow reference is using Log4j 1, so that isn’t a match.
Based on the fact that you are in ExtendedThrowablePatternConverter that would
imply that you are logging an exception. But I don’t know why you would be
getting stuck in there. While formatting the exception is slow, it
This looks similar:
http://stackoverflow.com/questions/15543521/mixed-usage-of-log4j-and-commons-logging-causes-a-class-loading-deadlock
But we don't use any other logging framework besides slf4j, log4j2 and log4j2
bridges.
On 2016-07-05 15:14 (-0400), "Leon Finker" wrote:
>