I've had a similar problem with Inprise server last year... Corba reference are not serializable and handles are zero'ed at passivation.
my solution was to copy the IOR of the reference in a member string at passivation, and resucitate it at activation. the idea to use Entity bean can be a good idea when the bean represent a "durable" "shared" "instance" of something having a separate indentity, not just an access tool to some "actions" > -----Message d'origine----- > De: Johnson, Lance [mailto:[EMAIL PROTECTED]] > Date: mardi 30 octobre 2001 00:18 > �: [EMAIL PROTECTED] > Objet: RE: [JBoss-user] CORBA client > Importance: Haute > > > We are in the process of developing an ejb that is a corba > client. One of > the drawbacks that I have seen so far is that when our EJB is > passivated we > must disconnect all CORBA connections. If we don't do this, > I think, we > will have CORBA object leaks in our jacOrb code. Then, when > it is activated > we have to reconnect to our servers (as needed). > > Is there a way to get around this overhead of disconnecting and > reconnecting? Can you turn off passivating and activating on > the container? > > Lance Johnson > e-mail: [EMAIL PROTECTED] _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
