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 » getJDBCType4Connection delay

Post new topic  Reply to topic
 getJDBCType4Connection delay « View previous topic :: View next topic » 
Author Message
Algol
PostPosted: Mon Jan 23, 2017 1:48 am    Post subject: getJDBCType4Connection delay Reply with quote

Novice

Joined: 23 Jan 2017
Posts: 13
Our project (IIB 9.0.0.6) has to integrate several Oracle databases. So, we use MbJavaComputeNodes and take connection using getJDBCType4Connection method. Some our flows require consecutive and repeated connections to datasources like A-B-A.
And there we have a problem with delay - third MbJavaComputeNode node calls getJDBCType4Connection - the same way as first one:
Connection conn = getJDBCType4Connection("A", JDBC_TransactionType.MB_TRANSACTION_AUTO);
and it takes more than 60 seconds and resulting connection is different from retrieved in first MbJavaComputeNode (logged with hashCode).
For analysis we deleted all calls except the getJDBCType4Connection - "A" datasource in first and third node and "B" datasource in second node. Result is the same.
What's going on there?
And there are nothing special in datasources properties (BTW, maxConnectionPoolSize=0 does not affect on the behavior). Like:
A
connectionUrlFormat='jdbc:oracle:thin:@[serverName]:[portNumber]:[connectionUrlFormatAttr1]'
connectionUrlFormatAttr1='work'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='a'
databaseSchemaNames='useProvidedSchemaNames'
databaseType='Oracle'
databaseVersion='default_Database_Version'
description='Simplified Database Routing Sample Database'
environmentParms='default_none'
jarsURL='c:\ProgramData\IBM\MQSI\shared-classes\'
jdbcProviderXASupport='jdbcProviderXASupport'
maxConnectionPoolSize='10'
portNumber='1521'
securityIdentity='ASecurityIdentity'
serverName='server1' type4DatasourceClassName='oracle.jdbc.xa.client.OracleXADataSource'
type4DriverClassName='oracle.jdbc.OracleDriver'
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Jan 23, 2017 8:12 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
Talk to your DB Admins...

And then both of you go to your network team and ask them to explain what they did...
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Algol
PostPosted: Tue Jan 31, 2017 3:23 am    Post subject: Reply with quote

Novice

Joined: 23 Jan 2017
Posts: 13
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac00390_.htm
"The most important property concerned with transactions on distributed systems is Coordinated Transaction. By default, this property is cleared (not selected), which means the message flow is partially coordinated and the broker commits or rolls back the message flow transaction. If you select this property, the input node calls the external transaction manager WebSphere MQ for commit and rollback processing."
Looks like Message Broker coordinated transactions have some problems when a flow requres several connections to the same datasource.
After configuring of MQ Trsansaction Manager (XA Resource configuring is not so easy and requires several changes of SwitchFile references) and deploy of globally coordinated flow everithing works fine - getJDBCType4Connection returns the same object (at least we see it by hashCode) and makes it very fast.
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 » getJDBCType4Connection delay
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.