My Oracle Support Banner

Failed To Use TAB File For MQ Connection (Doc ID 2925629.1)

Last updated on JUNE 04, 2024

Applies to:

Oracle SOA Suite - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

Unable to use TAB file to connect to MQ

[ERROR] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 005xxxxxxxxxyZ0000J2000Rmu,1:20912] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] [oracle.soa.tracking.FlowId: 246xxxx7] [oracle.soa.tracking.InstanceId: 227xxxxxx [oracle.soa.tracking.SCAEntityId: 150xx2] [composite_name: composite!1.0] [FlowId: 0000OGcZNf53n3b_lHd9iZ1ZN_Gd00006N] JCABinding=> DOMAIN: xxxxxxxxx:MqAdpEnqONEMDS.INSERVICE.INBOUND.LOCAL [ Enqueue_SyncCrew_ptt::Enqueue_UpdateUnit(body) ] Could not invoke operation 'Enqueue_UpdateUnit' against the 'mq' due to: [[
BINDING.JCA-12511
JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
DOMAIN: xxxxxxxxxxxxx:MqAdpEnqONEMDS.INSERVICE.INBOUND.LOCAL [ Enqueue_SyncCrew_ptt::Enqueue_UpdateUnit(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510
JCA Resource Adapter location error.
Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/>
The JCA Binding Component is unable to locate the Resource Adapter specified in the <connection-factory/> element: DOMAIN location='eis/MQ/PExxxxx'.
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or
2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/MQ/PExxxxx. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR).
Please correct this and then restart the Application Server

Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections.

]]

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.