| Author |
Message
|
| hilltops |
 Posted: Mon Apr 24, 2006 1:00 am Post subject: Pooling of JMS connections to JMS message server |
 |
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
Is the JMS connection factory object analogous to a JDBC connection factory in the sense of having a configurable number of connections to the underlying server and supporting the return of connections objects to the pool once they have been used?
It is not very obvious from looking at a basic JMS code what is really happen behind the scene.
Thankx |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Apr 24, 2006 4:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mvic |
| Posted: Mon Apr 24, 2006 5:21 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
I would have said no. The connection factory simply holds data used to initialise a connection. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Apr 24, 2006 5:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess it depends on if you're using it in a container or not...
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/umj_pqcfm.html
| Quote: |
Connection pool
Specifies an optional set of connection pool settings.
Connection pool properties are common to all J2C connectors.
The application server pools connections and sessions with the JMS provider to improve performance. This is independent from any WebSphere MQ connection pooling. You need to configure the connection and session pool properties appropriately for your applications, otherwise you may not get the connection and session behavior that you want.
Change the size of the connection pool if concurrent server-side access to the JMS resource exceeds the default value. The size of the connection pool is set on a per queue or topic basis.
|
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| hilltops |
| Posted: Mon Apr 24, 2006 6:37 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
The foregoing implies that for a stand-alone application (ie not deployed within WAS) the connection pooling functionality is not available.
There's an attribute on the QueueConnectionFactory/TopicConnectionFactory called USECONNPOOLING(YES/NO) implying that thes factories hold pooled connections. But this does not tell you how many connection there are or whether these can be configured. |
|
| Back to top |
|
|
|
|
