Each stateless bean could simply hold onto a JMS connection. The stateless
beans themselves act as a pool (assuming your J2EE server does this).
If you need to JMS connection pool size to be different than the stateless
bean pool size, then you can implement a helper class and JVM singleton that
manages the JMS connection pool.
I have a goodie that does generic object pooling if anyone is interested. It
is pretty simplistic (e.g. pools are fixed size and don't grow or shrink).
Regards,
-Chris.
> -----Original Message-----
> From: Aravind Naidu [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, February 28, 2000 8:10 AM
> To: [EMAIL PROTECTED]
> Subject: JMS Connection pooling in a Stateless Session Bean
>
> Hi,
> I have a set of stateless Session Beans that talk to JMS to obtain some
> data
> from legacy systems via MQ.
>
> What is the best way of implementing some sort of connection pooling so
> that
> I don't have to open JMS connections and sessions every time ?
>
> Regards,
> Aravind
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
