| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Database connection pooling |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sam99 |
 Posted: Wed Sep 19, 2012 8:11 am Post subject: Database connection pooling |
 |
|
Apprentice
Joined: 19 Jul 2012
Posts: 43
|
Hello MB Guru's ,
We are using ComputeNode/DatabaseNode for accessing SQLServer Database.
Is there any way we can control database connection pooling ?
Are there any best practises for database connectivity ?
I have read a IBM MB document regarding database connection, details are provided below
The broker requires a database connection for each data source name (DSN) that is referenced in the message flow, even if different DSNs resolve to the same physical database. The number of connections to a user database that a broker requires depends on the actions of the message flows that access the database. For each message flow thread, a broker that accesses a user database makes one connection for each data source name (DSN). If a different node on the same thread uses the same DSN, the same connection is used, unless a different transaction mode is used, in which case another connection is required.
When you start a broker, and while it is running, it opens connections to WebSphere® MQ queues and to databases. The broker makes the connections when it needs to use them, and they remain open until one of the following events occurs:
• The message flow has been idle for 1 minute
• The message flow is stopped
• The broker is stopped
Thanks |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Sep 19, 2012 8:15 am Post subject: Re: Database connection pooling |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Hi Sam. Welcome to the party.
| Sam99 wrote: |
| Is there any way we can control database connection pooling ? |
No, although there is an : r f e : requesting same. rekarm is not convinced that it is needed, however.
| Sam99 wrote: |
| Are there any best practises for database connectivity ? |
In its current state, WMB is mediocre at best in directly accessing the database. If you have high volume or low latency requirement, you might consider using solidDb between WMB and your database to improve performance.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Wed Sep 19, 2012 11:31 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi Sam99,
You can find some more information by keywords: maxConnectionAge and MQSI_DATABASE_IDLE_CONNECTIONS_DONT_ENDINSTANCE
--
Marko |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sat Sep 22, 2012 5:53 pm Post subject: Re: Database connection pooling |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| Sam99 wrote: |
| Is there any way we can control database connection pooling ? |
As each message flow instance manages its own database connections, the most obvious way to control the number of database connections is to control the number of message flow instances.
| marko.pitkanen wrote: |
| You can find some more information by keywords: maxConnectionAge and MQSI_DATABASE_IDLE_CONNECTIONS_DONT_ENDINSTANCE |
Note that these options affect how the broker manages idle connections, not active connections. |
|
| 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
|
|
|
|
