It looks like this is a bug if coming from a client-application. It seems
if you create a initial context within the same instance of a class, and
then close and try to re-open another InitialContext it will fail. I tested
this again today making my test class runnable and spawning three instances
of it off into three threads. This works fine, but if you attempt to make
the same instance of one of the threads call InitialCOntext twice(after
closing and setting it to null just in case) it throws the
NullPointerException. I am currently in conversation with Karl about this.
It has been reported as bug #210,215, & 216. Hopefully this will get
resolved soon. Curruently it is forcing us to look at other servers as a
fallback plan until this can be fixed.
Later....
Greg
-----Original Message-----
From: Guilherme Ceschiatti [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 03, 2000 9:12 AM
To: Orion-Interest
Subject: More than one InitialContext
Hi.
I'd like to konw if it's possible to have more than on InitialContext in the
same app, one for each app server I have.
--
[]s
Guilherme Ceschiatti
http://listando.net
[EMAIL PROTECTED]
