Obtaining initialcontext from t3 client leaks current thread

Question

Summary: creating an initial context from a t3 client leaks the current
thread.
NB: I posted about this problem recently, except that the initialcontext was
obtained from
within the Weblogic server. I was told that user threads should not be
spawned from within
the server. I've since discovered that the problem also exists from a T3
client as well.
Any solutions/workarounds?
Our temporary workaround is to maintain our own thread pool, and never
expire threads
out of the pool. That appears to mitigate the problem, but I'm a little
leery of reusing
threads when it appears as though parts of Weblogic key off the thread
object (this is
what seems to be causing the leak in the first place.) Is this a correct
workaround?
Regards,
-kb-
Sample output:
java -mx64m -ms64m com.snapfish.test.SimpleTestJVMSockHTTPClient: connect() success to host: localhost port: 7001 sockID: 4
Avail mem is 66325400
Avail mem is 66240784
Avail mem is 66139744
Avail mem is 66038672
Avail mem is 65937600
Avail mem is 65836528
Avail mem is 65735456
Avail mem is 65634392
Avail mem is 65533240
Avail mem is 65432208
-- SimpleTest.java --
package com.snapfish.test;
import java.util.Properties;
import javax.naming.InitialContext;
import javax.naming.Context;
public class SimpleTest
public static void main(String arg[])
for (int i=0; i<1000; i++) {
Thread t = new Thread () {
public void run() {
try {
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL,
"http://localhost:7001");
InitialContext ctx = new InitialContext(p);
ctx.close();
ctx = null;
catch (Exception ex) {
ex.printStackTrace();
return;
private byte buf[] = new byte[100000];
t.start();
try {  t.join(); }
catch (InterruptedException ex) {
ex.printStackTrace();
return;
t = null;
System.gc();
System.out.println("Avail mem is
"+Runtime.getRuntime().freeMemory());

Answer 1

You will need the generated stubs packaged on the client side.