This is a good idea. I am just worried that it will not work. While I haven't worked with Database connection pooling in EJBs yet, the way I understand it the container creates the connections (i.e. the ejb developer informs the container what connections to make). Having this knowledge is crucial for connection pooling. CORBA connections are created and maintained by the ORB (JacORB in my case). Unless there is some collaboration between the container and the ORB I don't see how it could work. What do you guys think? If anyone does some tests on this let the list know.
Thanks, Lance Johnson e-mail: [EMAIL PROTECTED] -----Original Message----- From: Weir, John [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 30, 2001 8:16 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] CORBA client Is it possible to maintain the connections in a connection pool ? This is a similar issue to Database Connections and the pooled approach works there Just a thought J -----Original Message----- From: Jean-Christophe Pazzaglia [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 30, 2001 2:04 PM To: Johnson, Lance Cc: [EMAIL PROTECTED] Subject: Re: [JBoss-user] CORBA client "Johnson, Lance" wrote: > 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). it is exactly what I 'm doing too ... > Is there a way to get around this overhead of disconnecting and > reconnecting? Can you turn off passivating and activating on the container? it seems to me a bad idea to do it (seems to brake the idea behind the EJB stuff) but I remenber to have seen some parameters for the cache ... so I conclude that you too create your 'corba' ejb as 'session bean', I was wondering if 'pure' ejb-proxy for corba service (*) should not be seen as sometime as 'entity'(bean managed) or even stateless ejb ? Finally what about an ejb which is a corba server, somebody tried that ? jc (*) I mean ejb which enable to reach all corba services by forwarding the call withou adding 'intelligence' _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
