| Author |
Message
|
| sudhir |
 Posted: Wed Mar 23, 2011 4:00 am Post subject: JDBC connectivity issue in WMB V7 |
 |
|
Novice
Joined: 17 Dec 2002
Posts: 20
Location: Pune, India
|
Hi All,
We are facing problem with JBDB connectivity through JAVa compute Node. Oracle Database(10g) is on AIX and MB runtime is on AIX
Following are the details of JDBCProvider
JDBCProviders
DBEIWS1
connectionUrlFormat='jdbc:oracle:thin:uatuser/uatuser@10.77.16.49:1526:DBEIWS1'
connectionUrlFormatAttr1='DBEIWS1'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='DBEIWS1'
databaseType='Oracle'
databaseVersion='default_Database_Version'
description='Simplified Database Routing Sample Database'
environmentParms='default_none'
jarsURL='/home/wbiadmin/jdbc/lib'
maxConnectionPoolSize='0'
portNumber='1526'
securityIdentity='jdbc_SecurityIdentity'
serverName='10.77.16.49'
type4DatasourceClassName='oracle.jdbc.xa.client.OracleXADataSource'
type4DriverClassName='oracle.jdbc.OracleDriver'
We are getting following exception in error message
[BIPmsgs:6268]BIP6268E: A connection error has occured for JDBC provider 'DBEIWS1'.
The broker will attempt to reconnect to the JDBC provider. Exception details: ..
The JDBC connection to the JDBC provider has ended for the reasons given by the exception details. ..
Contact your WebSphere Message Broker administrator. : Broken Connection found at transaction start
MB syslog is given below
***********************
Mar 23 17:07:30 EAIStaging user:info WebSphere Broker v7001[466978]: (MBBROKER.EG_COM_SRV)[6946]BIP4362E: Java node error: Caught unexpected XAException. Message: null Error code: -3 Oracle ErrorCode: 65535. : MBBROKER.4f0d03cd-2e01-0000-0080-b5784649ee9e: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 692: JDBCType4SinglePhaseTrxnhandlerErrors::logXAException(): :
Mar 23 17:07:30 EAIStaging user:info WebSphere Broker v7001[466978]: (MBBROKER.EG_COM_SRV)[6946]BIP4362E: Java node error: Caught unexpected XAException. Message: null Error code: -3 Oracle ErrorCode: 65535. : MBBROKER.4f0d03cd-2e01-0000-0080-b5784649ee9e: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 692: JDBCType4SinglePhaseTrxnhandlerErrors::logXAException(): :
Mar 23 17:07:30 EAIStaging user:info WebSphere Broker v7001[466978]: (MBBROKER.EG_COM_SRV)[6946]BIP4362E: Java node error: Error Committing Transaction for JDBC DataSourceName DBEIWS1. : MBBROKER.4f0d03cd-2e01-0000-0080-b5784649ee9e: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 692: JDBCType4SinglePhaseTrxnTable::commit: :
***********************************
Another observation that we found, we are able to process alternate request.
Please let us know why this error is coming. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Mar 23, 2011 4:03 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
When you execute this, what is the output?
| Code: |
| mqsireportproperties broker_name -c JDBCProviders -a -o AllReportableEntityNames |
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| sudhir |
| Posted: Wed Mar 23, 2011 4:08 am Post subject: |
|
|
Novice
Joined: 17 Dec 2002
Posts: 20
Location: Pune, India
|
Output for the command : mqsireportproperties MBBROKER -c JDBCProviders -a -o AllReportableEntityNames
JDBCProviders
DB2
Informix
Informix_With_Date_Format
Microsoft_SQL_Server
Oracle
Sybase_JConnect6_05
Teradata
solidDB
DBEIWS1
and for Particular Oracle JDBCProvider(DBEIWS1) is given below:
[wbiadmin@EAIStaging:/var/mqm/qmgrs/MBQMGR]$ mqsireportproperties MBBROKER -o DBEIWS1 -c JDBCProviders -r
JDBCProviders
DBEIWS1
connectionUrlFormat='jdbc:oracle:thin:uatuser/uatuser@10.77.16.49:1526:DBEIWS1'
connectionUrlFormatAttr1='DBEIWS1'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='DBEIWS1'
databaseType='Oracle'
databaseVersion='default_Database_Version'
description='Simplified Database Routing Sample Database'
environmentParms='default_none'
jarsURL='/home/wbiadmin/jdbc/lib'
maxConnectionPoolSize='0'
portNumber='1526'
securityIdentity='jdbc_SecurityIdentity'
serverName='10.77.16.49'
type4DatasourceClassName='oracle.jdbc.xa.client.OracleXADataSource'
type4DriverClassName='oracle.jdbc.OracleDriver'
BIP8071I: Successful command completion. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Mar 23, 2011 4:14 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Can you change the line that says:
| Quote: |
databaseVersion='default_Database_Version'
|
to a realistic value and retry?
My main expertise is with WMB/DB2 so someone else with WMB/Oracle experience may be more helpful.
From a command line on this system, using a jar with JDBC calls, are you able to successfully execute this jar that connects to this instance and do stuff like SELECT * ?
Like the code to connect would be:
| Quote: |
Class.forName(driver); // load Oracle driver
conn = DriverManager.getConnection(url, username, password);
|
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 23, 2011 4:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
A broken connection usually indicates a network or firewall error.
In this case, it could potentially indicate that you are trying to connect to multiple Oracle RAC instances and one of the instances is unreachable or unavailable.
That would also coincide with being able to process alternate messages - that each message that fails goes to the bad RAC instance and each message that succeeds goes to the good RAC instance.
So the first thing to do is determine if you are talking to a RAC. If you are, then that is where the problem is, not in your code or in Broker but in the network or the RAC. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 23, 2011 6:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And if he is talking to a RAC, I would also suggest him to talk to the corresponding Oracle DBAs to make sure his URL connect string is suitable for the RAC. Connection purge policy may also need to be considered. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rrydziu |
| Posted: Wed Dec 21, 2011 2:02 am Post subject: |
|
|
Newbie
Joined: 21 Dec 2011
Posts: 8
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 21, 2011 2:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you had the same problem, it's very very likely that you made the same mistake as the original poster, which is that you configured the ConnectionURLFormat incorrectly.
To everyone reading this thread - the connectionURLFormat in these posts IS WRONG. IT HAS REAL DATA IN IT, AND IS NOT A PATTERN.
It should not be 'jdbc:oracle:thin:uatuser/uatuser@10.77.16.49:1526:DBEIWS1'. IT should have been LEFT ALONE and be more like 'jdbc:oracle:thin:[user]/[password]@[servername]' or etc. |
|
| Back to top |
|
|
| rrydziu |
| Posted: Wed Dec 21, 2011 3:58 am Post subject: |
|
|
Newbie
Joined: 21 Dec 2011
Posts: 8
|
| mqjeff wrote: |
If you had the same problem, it's very very likely that you made the same mistake as the original poster, which is that you configured the ConnectionURLFormat incorrectly.
To everyone reading this thread - the connectionURLFormat in these posts IS WRONG. IT HAS REAL DATA IN IT, AND IS NOT A PATTERN.
It should not be 'jdbc:oracle:thin:uatuser/uatuser@10.77.16.49:1526:DBEIWS1'. IT should have been LEFT ALONE and be more like 'jdbc:oracle:thin:[user]/[password]@[servername]' or etc. |
Hi,
I have made my conf. properties based on template, so I have it more or less proper:
| Code: |
connectionUrlFormat='jdbc:oracle:thin:[user]/[password]@[serverName]:[portNumber]:[connectionUrlFormatAttr1]'
connectionUrlFormatAttr1='ESBT1'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='ESBT1'
databaseType='Oracle'
databaseVersion='11.2.0.2'
description='XXXX_MOCK_DEV_Database'
environmentParms='default_none'
jarsURL='/opt/jdbc'
maxConnectionPoolSize='0'
portNumber='1521'
securityIdentity='XXXX_MOCK_SecIdent'
serverName='10.43.39.30'
type4DatasourceClassName='oracle.jdbc.xa.client.OracleXADataSource'
type4DriverClassName='oracle.jdbc.OracleDriver'
|
so I'm quite sure that problem in my situation was with driver. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 21, 2011 4:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| rrydziu wrote: |
| so I'm quite sure that problem in my situation was with driver. |
Okay. Good work! 
But it still needed to be said that this thread represents a bad configuration. Since neither of the other two people who had originally replied to the original message had mentioned it... |
|
| Back to top |
|
|
| rrydziu |
| Posted: Wed Dec 21, 2011 6:20 am Post subject: |
|
|
Newbie
Joined: 21 Dec 2011
Posts: 8
|
I agree, but for bad url (like here) I have different exception:
| Code: |
)[4]BIP6233E: An error occurred in node: Java Compute There was a problem establishing a connection to the given database URL: datasource URL = jdbc:oracle:thin:radek/radek@10.43.39.30:1521:ESBT1 Exception details: Invalid argument(s) in call : MB7BROKER.ffcbe902-3301-0000-0080-ee5fd10afffb: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 717: JDBCType4Connection::createXAConnection: :
|
I have found also different topic
http://www.mqseries.net/phpBB2/viewtopic.php?t=58708
which have exactly the same problem (without solution). |
|
| Back to top |
|
|
|
|
