Concurrent access to initial context?

Question

Using WebLogic Server 6.0
I wrote a simple stand alone Java client (see code below) that
performs the following steps:
1. Gets the Initial Context for the WLS JNDI
2. Closes the initial context
3. Goes into an indefinite loops (to keep the client alive)
I start up one client and it performs steps 1, 2, and 3 and is
sitting at step3.
Then I start up another client. It hangs at step 1 until I kill
the first client.
It cannot obtain the initial context while the first client is
running.
I do not understand this behavior! Is this behavior correct?
If so, could somebody
explain why it works this way. The initial context is used to
lookup our EJBs. If two
clients cannot access the Initial Context at the same time, won't
this be a major
bottle neck when using EJBs?
Please help!
Here's is the code for the client....
public static void main(String args[])
     try
     Context ctx = null;
     System.out.println("Before get context.");
     Hashtable env = new Hashtable();
     env.put(Context.INITIAL_CONTEXT_FACTORY,
          "weblogic.jndi.WLInitialContextFactory");
     env.put(Context.PROVIDER_URL,
          "t3://localhost:7001");
     ctx = new InitialContext(env);
     System.out.println("Initial context created.");
     ctx.close();
     System.out.println("Closed context.");
     // Hang
     while(true){}
     catch (Exception e)
     e.printStackTrace();

Answer 1

Yes - it was the CPU problem. If I use Thread.sleep(...) it works fine.
I had a feeling it was a mistake on my part. Thanks for the help.
Robert Patrick <[email protected]> wrote:
There is definitely something else going on here. Try adding a
Thread.sleep(1000) inside your while loop to prevent the process from
spinning and eating up all the CPU...
MK Parini wrote:
Using WebLogic Server 6.0
I wrote a simple stand alone Java client (see code below) that
performs the following steps:
1. Gets the Initial Context for the WLS JNDI
2. Closes the initial context
3. Goes into an indefinite loops (to keep the client alive)
I start up one client and it performs steps 1, 2, and 3 and is
sitting at step3.
Then I start up another client. It hangs at step 1 until I kill
the first client.
It cannot obtain the initial context while the first client is
running.
I do not understand this behavior! Is this behavior correct?
If so, could somebody
explain why it works this way. The initial context is used to
lookup our EJBs. If two
clients cannot access the Initial Context at the same time, won't
this be a major
bottle neck when using EJBs?
Please help!
Here's is the code for the client....
public static void main(String args[])
try
Context ctx = null;
System.out.println("Before get context.");
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL,
"t3://localhost:7001");
ctx = new InitialContext(env);
System.out.println("Initial context created.");
ctx.close();
System.out.println("Closed context.");
// Hang
while(true){}
catch (Exception e)
e.printStackTrace();