Thanks a lot. Regards,
Ali Sadik Kumlali ----- Original Message ---- From: James Strachan <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, January 15, 2007 12:00:09 PM Subject: Re: Proper way of pooling connections and sessions On 1/14/07, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote: > Hi folks, > > For a long time, I've been in search of an appropriate way of pooling > Connection and/or Session objects for both sender and the receiver sides. > Some solutions, such as MDBs, are only target the receiver side which are not > sufficient for the most cases. > > I've looked into three different approaches: MDB, JCA and Messenger > framework[1]. Neither of them have seemed perfect. So, I decided to list some > pros and cons of those (according to my understanding of course :-) > > Could someone shed some light on these? A pretty good summary. Some further points. MDBs sit on top of JCA anyway. Most J2EE containers provide a JMS facade which uses the JCA container underneath as well. So JCA is your best option if you want inbound and outbound pooling of connections & sessions. > JCA > ----- > - Need a container (J2EE or Spring + Jenks) > - Need a JCA adapter for the given container. For example, JCA adapter for > Jenks, WebLogic, WebSphere,... > - Both the sender and receiver are able to use it via JNDI lookup. > - JCA automatically handles connection pool on both incoming and outgoing > directions. > - What about session pool? JCA does that too > - What if my provider doesn't have a JCA adapter? Use genericjmsra > - What if I'm not able to use Spring and/or a J2EE container? You should probably use spring or J2EE if you want pooling for JMS. -- James ------- http://radio.weblogs.com/0112098/ ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index
