ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JDBC: Connection pool

Post new topic  Reply to topic
 JDBC: Connection pool « View previous topic :: View next topic » 
Author Message
zurg
PostPosted: Fri Aug 02, 2013 4:00 am    Post subject: JDBC: Connection pool Reply with quote

Novice

Joined: 04 Feb 2013
Posts: 10

Hello experts,

Probably a very stupid question...

Accoring to infocenter:

WebSphere® Message Broker manages JDBC connections in the following ways:
Non-pooled connections: xxx
Pooled connections: xxx

Source:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbj13600_.htm

But I have no idea how to switch before pooling/not-pooling connections for JDBC. I went through infocenter but was unable to find any hint...

The normal way, seems to be returning a pooled connection:
Code:
getJDBCType4Connection("XXX", JDBC_TransactionType.MB_TRANSACTION_AUTO);


I'm using WMB 8.0.0.2.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Aug 02, 2013 4:23 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Quote:
You can create a JDBC connection pool by setting the maxConnectionPoolSize property of the JDBCProviders configurable service to a non-zero integer value. The maxConnectionPoolSize property acts at the execution group level to specify the maximum number of JDBC connection threads that can be used. A value of zero defaults to the standard WebSphere Message Broker Version 8.0 behavior, where one JDBC connection is created for each message flow thread.


ie. Non-pooled.

To use pooled - set maxConnectionPoolSize to something other than zero.

Its not a dynamic item. You set it and forget it.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
zurg
PostPosted: Fri Aug 02, 2013 4:32 am    Post subject: Reply with quote

Novice

Joined: 04 Feb 2013
Posts: 10

lancelotlinc,

yes, you are right. Thank you.
I though the case is more complex but some additional tests shown that I'm wrong.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Aug 02, 2013 4:37 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Other important points:

Quote:
All message flows within an execution group that use the same JDBCProviders configurable service also share a connection pool. You can monitor the behavior of a JDBC connection pool by using broker resource statistics

The maxConnectionPoolSize property is applicable to JDBC connections obtained using the getJDBCType4Connection() API of the JavaCompute node, and to database operations in graphical data maps that are called by the Mapping node.

Note: The maxConnectionPoolSize property does not apply to the JDBC connections used by the DatabaseRetrieve or DatabaseRoute nodes.


getJDBCType4Connection() is the only way to use the pool, even if you have defined the maxConnectionPoolSize to be pooled.

Monitor your pool availability using resource statistics.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Fri Aug 02, 2013 5:35 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

lancelotlinc wrote:
Other important points:

Quote:
All message flows within an execution group that use the same JDBCProviders configurable service also share a connection pool. You can monitor the behavior of a JDBC connection pool by using broker resource statistics

The maxConnectionPoolSize property is applicable to JDBC connections obtained using the getJDBCType4Connection() API of the JavaCompute node, and to database operations in graphical data maps that are called by the Mapping node.

Note: The maxConnectionPoolSize property does not apply to the JDBC connections used by the DatabaseRetrieve or DatabaseRoute nodes.


getJDBCType4Connection() is the only way to use the pool, even if you have defined the maxConnectionPoolSize to be pooled.

Actually what it says is that the Graphical Data Map will also use the pool.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JDBC: Connection pool
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.