|
Home > Archive > WebSphere Application Server > October 2006 > javax.jms.Connection and Service Integration Bus
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
javax.jms.Connection and Service Integration Bus
|
|
|
| We are developing a JMS application on WAS 6 cluster, with Workload Management topologies for SIB (partitioned queues).
Is it a good idea to create, for message producers, a single Javax.jms.Connection per Connection Factory and to cache it (consumers are MDBs)? Could this choice affect in any way the workload management behavior?
Thanks
| |
| David Currie 2006-10-25, 1:36 am |
| No - in general you should use the get/use/close model for connections
to allow the application server to manage the pooling. It depends on
your topology but typically the workload management is done on the send,
not on the connect.
Regards,
David
|
|
|
|
|