Can you cast some votes on 215/216 in buzilla, it may help fix this bug
faster.
-----Original Message-----
From: Peter van Rensburg [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 14, 2000 10:21 AM
To: Orion-Interest
Cc: 'Karl Avedal' (E-mail)
Subject: RE: More than one InitialContext
Hi
I have noticed a similiar issue. We have two frontend corba servers
communicating with a virtual application server. Latter is two orion servers
behind two Foundry Layer4/7 switches running symmetric load balancing. When
one application server goes down the switches moves future connections to
the remaining server. The corba servers sets up the InitialContext everytime
it speaks to the application servers. Depending in which stage the
connection were, a NamingException is thrown or the communication continues
after a brief pause (during switch over). When the corba servers do receive
a NamingException, it will continue communicating with the remaining
application server but locks up inside the InitialContext constructor
moments after that. It would appear that this constructor sets up the actual
connection to the application server or keep the persistent connection open.
A NullPointerException as outlined in Greg's mail below, is thrown when
trying to close the context (aka connection).
Even using the undocumented optioned dedicated.connection="true" one still
cannot call the close() method on the context. Has this method been
implemented at all? Using this option however causes the VM to run out of
memory eventually.
Karl, Greg, has any progress been made here? Any ideas as to what exactly is
wrong here?
Regards,
Peter van Rensburg
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of J Davis
> Sent: 12 December 2000 09:53
> To: Orion-Interest
> Cc: 'Karl Avedal' (E-mail)
> Subject: RE: More than one InitialContext
>
>
> 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]
>
>
>
