| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Connection Pool while working with JMS |
« View previous topic :: View next topic » |
| Author |
Message
|
| say_2_anil |
 Posted: Thu Nov 16, 2006 11:20 pm Post subject: Connection Pool while working with JMS |
 |
|
Newbie
Joined: 16 Nov 2006
Posts: 8
|
Hi,
with the following Administration command
DEF QCF(testQCF) HOST(localhost) PORT(1414) CHANNEL(SEV.CONN) QMGR(GER_Q) TRAN(client) USECONNPOOLING(Yes)
we can bind the QueueManager as QueueConnectionFactory onto JNDI namespace which supports Connection pooling,
Where can i configure the properties for the Connection pool.
Thanks,
Anil Kumar. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Nov 17, 2006 3:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
In the app server that is supplying the connection pool.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| say_2_anil |
| Posted: Fri Nov 17, 2006 4:45 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2006
Posts: 8
|
I am not using any AppServer here.
Had a MQSeries Server installed,
Using FileSystem service provider for binding the QueueManager and queue objects into JNDI namespace.
Had a JMS Client, which does lookup in the namespace and tries to connect to QueueManager.
in this context,
Do MQSeries provide any sort of Connection Pooling mechanism for me? or
Do i need to write my own code to implement connection pooling?
What will be the significance of USECONNPOOLING(Yes) While binding the QueueManager into JNDI namespace.
Thanks,
Anil Kumar. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Nov 17, 2006 5:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The queue manager doesn't provide any kind of connection pooling mechanism.
The WebSphere MQ Java API provides Application Server Facilities, which provide a connection pool.
With some dilligent searching you may find a few other posts on the topic that go into more detail.
But if you need app server facilities like connection pooling, THEN USE AN APP SERVER. WAS-Community Edition comes to mind.
JMS is a J2EE/JEE standard. That means ENTERPRISE. Why would you run an Enterprise level technology outside an Enterprise container?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
