MQSeries.net :: View topic - BIP6253E: Could not locate JDBC Provider entry

m.grzelak

Hello.

We have a problem with JDBC XA transactions on MQ/Broker. Because of the network firewall I changed the XAOpenString entry for XAResourceManager in qm.ini file from 'WHBP' to 'WHBP+SesTM=120+LogDir=/home/mqbrkr/xa_trace' which is not correct for JDBC configuration. After restarting MQ/Broker I changed it back to correct 'WHBP' but now I'm getting error spam:

user:err|error WebSphere Broker v8002[12779642]: (PI_BRK_D.default)[33198]BIP6253E: Error in node: recovery stage. Could not locate JDBC Provider entry 'WHBP+SesTM=120+LogDir=/home/mqbrkr/xa_trace' in the broker registry, which was given for the data source name property for this node. : PI_BRK_D.666df374-4201-0000-0080-f258e7b510b1: /build/slot1/S800_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 739: JDBCType4XAHandler::XA_RECOVER: :

user:warn|warning WebSphere Broker v8002[12779642]: (PI_BRK_D.default)[25618]BIP2633W: Warning when starting transaction coordinated by WebSphere MQ; MQBEGIN failed: MQCC=1; MQRC=2122; node 'ADAPT_SCHED_WHBP_W_T.Scheduler_TimeoutNotif'. : PI_BRK_D.666df374-4201-0000-0080-f258e7b510b1: /build/slot1/S800_P/src/DataFlowEngine/TimeoutControl/ImbTimeoutNotificationNode.cpp: 1743: ImbTimeoutNotificationNode::setupUow: ComIbmTimeoutNotificationNode: ADAPT_SCHED_WHBP_W_T#FCMComposite_1_1

Somehow Broker remembers the incorrect entry. Redeploying message flows, restarting MQ/Broker and recreating execution group didn't help. New transactions made by 'WHBP' works fine. With command dspmqtrn I see one transaction in-doubt:

AMQ7056: Transaction number 0,83464 is in-doubt.
XID: formatID 5067085, gtrid_length 15, bqual_length 4
gtrid [528B70752013970250495F514D5F44]
bqual [00000001]

But I can't resolve it:
bash-3.00$ rsvmqtrn -m PI_QM_D -b 0,83464
AMQ7055: The transaction number is not recognized.

Configuration:

MQ 7.1.0.2/Broker 8.0.0.2 on one machine with AIX 6.1.
Oracle 10.2.0.5 on another server, behind a firewall.

Broker name = 'PI_BRK_D'
MQ server name = 'PI_QM_D'
Oracle database name ='whtest'

JDBCProvider 'WHBP' configured on Broker:
connectionUrlFormat='jdbc:oracle:thin:***/***@***:1521:whtest'
connectionUrlFormatAttr1='whtest'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='whtest'
databaseSchemaNames='useProvidedSchemaNames'
databaseType='Oracle'
databaseVersion='10.2.0.5'
description='default_Description'
environmentParms='default_none'
jarsURL='/home/mqbrkr/lib'
jdbcProviderXASupport='jdbcProviderXASupport'
maxConnectionPoolSize='0'
portNumber='1521'
securityIdentity='WHBP'
serverName='***'
type4DatasourceClassName='oracle.jdbc.xa.client.OracleXADataSource'
type4DriverClassName='oracle.jdbc.OracleDriver'

qm.ini file:

(...)
XAResourceManager:
Name=whtest
SwitchFile=JDBCSwitch
XAOpenString=WHBP
ThreadOfControl=THREAD

We have a message flow (with coordinated transaction=on) named "ADAPT_SCHED_WHBP_W_T" that connects to the Oracle database via JDBC provider 'WHBP':
java.sql.Connection conn = getJDBCType4Connection("WHBP", JDBC_TransactionType.MB_TRANSACTION_AUTO);

Anyone had similar problem or has any idea how to resolve it?