Monday, April 4, 2011

ERRJMS_CONN_FAC_NOT_FOUND when using the JMS Adapter


When trying to produce a message to a WebLogic 11g file-based JMS queue using the JMS Adapter, you may experience the following error in the Fusion Middleware 11g console:
Error Message: {}bindingFault
Fault ID    default/JmsFileProduce!1.0*soa_1ae24984-e125-4da2-9f69-278670a0845e/JmsFileProduce/70022-BpInv0-BpSeq0.3-3
Fault Time    Mar 13, 2011 9:09:38 PM
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><bindingFault xmlns=""><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. JmsFileProduce:Jms [ Produce_Message_ptt::Produce_Message(commonMessage) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141 ERRJMS_CONN_FAC_NOT_FOUND. ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory jms/QueueConnectionFactory neither through JNDI nor instantiate it as a Java class. Please examine the log file to determine the problem. 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. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>jms/QueueConnectionFactory</detail></part><part name="code"><code>null</code></part></bindingFault></bpelFault>


1. Change the JNDI in the code to: eis/wls/Queue

Even though you may have created a connection factory "eis/Jms/PerfTestJMSFile" in the JMS Adapter, you have to use that default one.

Applicable Versions:
  • Oracle SOA Suite 11g (11.1.1.x)
  • Oracle WebLogic Server 11g (10.3.x)

Ahmed Aboulnaga


Unknown said...

it is not working for the default jndi name

Anonymous said...

It is working with default JNDI. But why it is not working with newly created?