Author |
Message
|
vinumon |
Posted: Thu May 15, 2014 5:34 am Post subject: performance issue for message flow with JDBC connectivity |
|
|
Acolyte
Joined: 06 May 2014 Posts: 59
|
We have 1 flow that is using JDBC connectivity . Sometimes the result from the database takes time. It is not occuring everytime. This is happening in Production environment.
Do we need to set any tuning parameter on Broker end ? |
|
Back to top |
|
 |
McueMart |
Posted: Thu May 15, 2014 5:51 am Post subject: |
|
|
 Chevalier
Joined: 29 Nov 2011 Posts: 490 Location: UK...somewhere
|
What kind of analysis have you done to ensure that the problem is with the Broker, and not with the database? |
|
Back to top |
|
 |
MQsysprog |
Posted: Thu May 15, 2014 5:54 am Post subject: |
|
|
Centurion
Joined: 24 Feb 2014 Posts: 116
|
Well probably the first thing to verify is the behaviour of the application ,mainly the amount and the type of operations requested on the db side when the response times are poor .
You could also expect db issues like locks on tables rows ,with concurrent updates and so on .
Here i am assuming the use of a relational DBM in your enviroment ... |
|
Back to top |
|
 |
vinumon |
Posted: Wed May 21, 2014 4:46 am Post subject: |
|
|
Acolyte
Joined: 06 May 2014 Posts: 59
|
In broker logs I seee error as " There was a problem releasing JDBC connection. Exception details: error message: IO Error: Connection reset, SQLState value:08006, vendor error code:17002, stack trace:[oracle.jdc.driver.T4CConnection.doCommit(T4CConnection.java:613) oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3674) oracle.jdbc.drivr.PhysicalConnection.commit(PhysicalConnection.java:3680) com.ibm.broker.jdbcnodes.JDBCConnection.releaseIdleDBConnections(JDBCConnection.java:394) . The node was unable to release an acquired JDBC database connection. |
|
Back to top |
|
 |
vinumon |
Posted: Tue Dec 09, 2014 5:25 am Post subject: |
|
|
Acolyte
Joined: 06 May 2014 Posts: 59
|
Hi,
Iam pointing to scan ip of DB. and configuration is as below
JDBCProviders
visidbnew
connectionUrlFormat='jdbc:oracle:thin:[user]/[password]@[serverName]:[portNumber]:[connectionUrlFormatAttr1]'
connectionUrlFormatAttr1='vsstgfd1'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='default_Database_Name'
databaseSchemaNames=''
databaseType='default_Database_Type'
databaseVersion='default_Database_Version'
description='vdbtest'
environmentParms='default_none'
jarsURL='/var/mqsi/odbc'
jdbcProviderXASupport='jdbcProviderXASupport'
maxConnectionPoolSize='0'
portNumber='1521'
securityIdentity='visnewSecurityIdentity'
serverName='10.0.41.132'
type4DatasourceClassName='oracle.jdbc.xa.client.OracleXADataSource'
type4DriverClassName='oracle.jdbc.OracleDriver'
If we point to scan ip the load will get distributed right ? |
|
Back to top |
|
 |
|