-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 We are using Tomcat 5.5.9, and am having a problem with a memory leak. Most of the threads in the thread dump have the similar stack trace as this one does.
It doesn't make sense, because it seems that the ldap connection came from the tomcat server, not from a web application. We don't have any authentication set up to go to the ldap from the Tomcat container, I do all my authenticating explicitly, through my web applications. How can I track down what is the cause of threads blocking going to the ldap? Thank you for any help. "Thread-21964" daemon prio=10 tid=0x0063aac8 nid=0x55dc runnable [0x6567f000..0x6567fa10] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:313) - locked <0xaaf005c8> (a java.io.BufferedInputStream) at com.sun.jndi.ldap.Connection.run(Connection.java:780) at java.lang.Thread.run(Thread.java:595) - -- "Love is mutual self-giving that ends in self-recovery." Fulton Sheen James Black [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD9IG1ikQgpVn8xrARA5eKAKCNUdAib9mAzSWHJiR5Kka+pBR+7wCaAiJp 8zIzvCV8yqdM8SoSeccVS6w= =yPeA -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]