https://bz.apache.org/bugzilla/show_bug.cgi?id=65553
--- Comment #4 from Michael Osipov <micha...@apache.org> --- (In reply to Thomas Hoffmann from comment #3) > Hello Michael, > if the leak is reported without using JNDIRealm, it might be > that your application creates an LDAP-Query or InitialDirContext without > closing it? > Maybe you can use a breakpoint in "com.sun.jndi.ldap.Connection" to see > which code is causing the thread to start. > I opened the bug because Tomcat is causing the thread to start, out of the > scope of the web-application. It can also happen that a web application > causes this leak report but then the application might be able to handle it. One of the reasons is https://github.com/spring-projects/spring-ldap/issues/489 I have reviewed other spots, but always close/release connections as well as naming enumerations. One reaons could be that I create test connection in startInternal and that could be subject to not the webapp classloader. I guess I have missed something. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
