| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JDBC Connection pool size |
« View previous topic :: View next topic » |
| Author |
Message
|
| GeneRK4 |
 Posted: Wed Aug 28, 2013 8:45 pm Post subject: JDBC Connection pool size |
 |
|
Master
Joined: 08 Jul 2013
Posts: 220
|
Please help me in finding out the solution for an issue we are facing in performance test...
We have 3 Execution groups for synchronous transactions and another 3 Execution Groups for Asynchronous transactions.
We have 2 brokers load balancing each other.So,totally we have 6 EGs for Synchronous and 6 for Asynchronous.
In each EG,the message flow connecting to Database through JDBC is deployed with 30 as instances count.So,totally we have ((30*3)+(30*3))*2=360 flows connecting to MySQL Database.JavaCompute node is used for connection.
The Maximum connection pool defined in each EG is 100.
At MySQL system,the maximum connections is defined as 500.
When we are doing 120 (60 synch+60 asynch) messages/second in performance test for 10 mins contiuously,we are getting,Connection pool not available,JDBC Null Pointer exception.
We are monitoring in Resource Statistics.We could see the Actual JDBC connection pool being utilisted in each EG seems to be only 18 to 34.(100 is the maximum defined).
We are not sure where we need to tune up the connections.
Out of 20000 messages ,atleast 100 are failing with Null pointer exception(connections not available).
please kindly help me urgently...We have only 2 days time for go live... |
|
| Back to top |
|
 |
| nukalas2010 |
| Posted: Thu Aug 29, 2013 3:59 am Post subject: Re: JDBC Connection pool size |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
| GeneRK4 wrote: |
Please help me in finding out the solution for an issue we are facing in performance test...
We have 3 Execution groups for synchronous transactions and another 3 Execution Groups for Asynchronous transactions.
We have 2 brokers load balancing each other.So,totally we have 6 EGs for Synchronous and 6 for Asynchronous.
In each EG,the message flow connecting to Database through JDBC is deployed with 30 as instances count.So,totally we have ((30*3)+(30*3))*2=360 flows connecting to MySQL Database.JavaCompute node is used for connection.
The Maximum connection pool defined in each EG is 100.
At MySQL system,the maximum connections is defined as 500.
When we are doing 120 (60 synch+60 asynch) messages/second in performance test for 10 mins contiuously,we are getting,Connection pool not available,JDBC Null Pointer exception.
We are monitoring in Resource Statistics.We could see the Actual JDBC connection pool being utilisted in each EG seems to be only 18 to 34.(100 is the maximum defined).
We are not sure where we need to tune up the connections.
Out of 20000 messages ,atleast 100 are failing with Null pointer exception(connections not available).
please kindly help me urgently...We have only 2 days time for go live... |
What is the version you are using?? We had faced a similar issue when we was on 7.0.0.1, and it got solved after upgrading to 7.0.0.6. |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Fri Aug 30, 2013 5:16 am Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
We are using WMB version 8.0.0.2  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 30, 2013 5:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So you're using a JDBCProvider configurable service?
And you're using the same service for all flows in all EGs?
And your JCN isn't doing anything to synchronize the access to the database?
And you see that you are running all instances of all flows at least sometimes? |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Fri Aug 30, 2013 8:06 am Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
| mqjeff wrote: |
| So you're using a JDBCProvider configurable service? |
Yes .I am
| mqjeff wrote: |
| And you're using the same service for all flows in all EGs? |
As I refer to IBM manual,it says,the connection pool size we define is actually EG
level.
We have only one flow connecting to Database in an EG.Hence Maxconnectionpoolsize=100 is utilised by the flow completely in an EG.
I could see this in Resource Statistics as well.For each EG,it shows 100 as Max. Connection Pool
For your reference: http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbj13600_.htm
| mqjeff wrote: |
| And your JCN isn't doing anything to synchronize the access to the database? |
I am not sure about this.Could you please elaborate?
As far as I read the IBM manual,it shows JCN has a feature in itself to close the JDBC connection idle for 15 mins.
And you see that you are running all instances of all flows at least sometimes?[/quote]
I didnt check that.I will take this into account for the next load run.It is going to happen in 2 days.I will check this and update. |
|
| 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
|
|
|
|
