Re: AW: AW: Orphaned thread by JNDIRealm / clearReferencesThreads reports memory leak

2021-09-06 Thread Mark Thomas
tober release round. Mark Thank you and have a good start into the new week! Thomas -Ursprüngliche Nachricht- Von: Mark Thomas Gesendet: Montag, 6. September 2021 09:36 An: users@tomcat.apache.org Betreff: Re: AW: Orphaned thread by JNDIRealm / clearReferencesThreads reports memory

AW: AW: Orphaned thread by JNDIRealm / clearReferencesThreads reports memory leak

2021-09-06 Thread Thomas Hoffmann (Speed4Trade GmbH)
Betreff: Re: AW: Orphaned thread by JNDIRealm / clearReferencesThreads reports memory leak Hi Thomas. Got it. I think it would be best if you opened a Bugzilla entry for this. One view is that the JRE should not be doing this - or at least doing it in a way that doesn't run the risk of memory

Re: AW: Orphaned thread by JNDIRealm / clearReferencesThreads reports memory leak

2021-09-06 Thread Mark Thomas
Hi Thomas. Got it. I think it would be best if you opened a Bugzilla entry for this. One view is that the JRE should not be doing this - or at least doing it in a way that doesn't run the risk of memory leaks in a Java EE / Jakarta EE environment. We have raised JRE bugs for issues like this

AW: Orphaned thread by JNDIRealm / clearReferencesThreads reports memory leak

2021-09-05 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello Mark, thanks for your reply. I already tried that option. But this flag only controls, how the InitialDirContext is created. The worker thread within com.sun.jndi.ldap.Connection is created with that corresponding classloader the first time. The problem is when the worker-thread within th