ORABPEL-12141 JMS Adapter

BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 more

Similar Messages

JMS-Adapter with persistent Queues (DB): ORABPEL-12166

Hi,
does anybody know what the error:
file:/C:/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/Provisioning/tmp/.bpel_SenderProvisioning_1.0_bb735430814144c8f5f279c73842c3d4.tmp/JMS_Provisiong_A.wsdl [ Produce_Message_ptt::Produce_Message(Request) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_ENQUEUE_ERR.
Die Nachricht konnte aufgrund von folgender Fehlerbedingung nicht in die Queue gestellt werden:.
; nested exception is:
ORABPEL-12166
ERRJMS_ENQUEUE_ERR.
Die Nachricht konnte aufgrund von folgender Fehlerbedingung nicht in die Queue gestellt werden:.
Weitere Informationen hierzu finden Sie in der Log-Datei.
means?
Where can i find the logs?

This is most likely caused by a nonexistent or misconfigured queue.
For a JMS adapter, make sure your AQ queue/topic is set up as JMSType. Make sure you've spelled everything correctly.
To find the logs for ESB go to:
$ORACLE_HOME/j2ee/oc4j_soa/log/oc4j see log.xml
For BPEL go to
$ORACLE_HOME/bpel/domains/default/logs see domain.log
You may also find errors in the OPMN logs:
$ORACLE_HOME/opmn/logs
see default_group~oc4j_soa~default_group~1.log
You will have to turn up log levels to "FINE" or "FINER" for ESB or DEBUG for BPEL to get anything close to a meaningful message. For my most recent error on ESB the "FINER" setting yielded the following message for this error:
</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[ORABPEL-12166
ERRJMS_ENQUEUE_ERR.
Could not enqueue message due to the following error condition:.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:237)
at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:143)
at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:197)
at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:156)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:485)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:736)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:497)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:430)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:447)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:184)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:112)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:106)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:85)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:105)
at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:273)
at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:212)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:197)
at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:82)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:69)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(ESBListenerImpl.java:369)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(ESBListenerImpl.java:295)
at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:293)
at oracle.tip.adapter.jms.inbound.JmsConsumer.doSend(JmsConsumer.java:571)
at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:507)
at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:353)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:274)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.UnsupportedOperationException: publish is called without a valid Topic
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1252)
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:215)
... 34 more
Hope that helps. See the SOA admin guide for help with setting log levels:
Here's where you can find all App Server books for SOA Suite:
http://download-west.oracle.com/docs/cd/B31017_01/nav/docindex.htm
Peace,
G.

Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ

Hi,
I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
I have updated the oc4j-ra.xml with the following inputs:
<connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
          <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
          <config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
          <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
          <config-property name="isTopic" value="false"/>
          <config-property name="isTransacted" value="true"/>
          <config-property name="username" value="admin"/>
          <config-property name="password" value="welcome"/>
     </connector-factory>
But while testing the BPEL process, I get the error:
<remoteFault>
<part name="code" >
<code>null</code>
</part>
<part name="summary" >
<summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
</part>
<part name="detail" >
<detail>null</detail>
</part>
</remoteFault>
Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
Thanks,
Jayatu

I am experiencing the exact same issue while configuring for Tibco EMS!!!
I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

Sensors in BPEL (JMS Adapter)

Hi there! I'm trying to send Sensor-Data into a MQQueue, but this always results in an
error. The results are in the following Error-Log (sorry, some messages are german but the
messages are nearly equal to english):
Caused by: ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Instanziieren von Connection Factory nicht möglich. JMS-Adapter konnte Connection Factory com.ibm.mq.jms.MQQueueConnectionFactory weder JNDI nicht finden noch als Java-Klasse instanziieren
Weitere Informationen hierzu finden Sie in der Log-Datei.
     at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:207)
     at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:98)
     at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:191)
     at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:132)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:426)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:417)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:380)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:104)
     at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
     at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:125)
     at com.collaxa.cube.engine.sensor.sa.publisher.JMSAdapterPublisher.publish(JMSAdapterPublisher.java:277)
     at com.collaxa.cube.engine.sensor.sa.FilteredDataPublisher.publish(FilteredDataPublisher.java:99)
     at com.collaxa.cube.engine.sensor.sa.BpelPublisher.publish(BpelPublisher.java:129)
     ... 83 more
Caused by: javax.naming.NameNotFoundException: com.ibm.mq.jms.MQQueueConnectionFactory not found
     at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
     at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:257)
The following Steps were made:
- I added two library-paths in the application.xml (D:\Programme\SOA_Suite\10.1.3.1\OracleAS_1\j2ee\oc4j_soa\config\application.xml)
<library path="../../home/lib/com.ibm.mq.jar"/>
<library path="../../home/lib/com.ibm.mqjms.jar"/>
- In the oc4j-ra.xml (D:\Programme\SOA_Suite\10.1.3.1\OracleAS_1\j2ee\oc4j_soa\application-deployments\default\JmsAdapter\oc4j-ra.xml)
a new connector-factory was added
     <connector-factory location="eis/mqseries/Queue" connector-name="Jms Adapter">
          <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
          <config-property name="factoryProperties" value="QueueManager=MQ_TEST;TransportType=1;HostName=10.1.1.1;Port=1414;Channel=SYSTEM.DEF.TEST"/>
          <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
          <config-property name="isTopic" value="false"/>
          <config-property name="isTransacted" value="true"/>
          <config-property name="username" value=""/>
          <config-property name="password" value=""/>
          <connection-pooling use="none">
          </connection-pooling>
          <security-config use="none">
          </security-config>
     </connector-factory>
I assume I have to enter a new JNDI-Entry somewhere but the JNDI-Browser in the Application Server is readonly.

There are two ways to get data into BAM. There is the ADC web service that BPEL uses and then there's Enterprise Link which is the ETL tool that can grab data from Databases and other sources. I only used EL for jms and for ETLing data into a a BAM data object, I never used it for real time. The only real time BAM I've done is with BPEL projects with BAM sensors. I don't think EL is sophisticated enough for looking for changes in rows of data.
Maybe you can have a db trigger that publishs the changed data to table specially designed for your task. Then you can create an EL "Plan" that runs periodically at a high enough rate that it appears to be in real time in BAM.
Another possibility is to have the db trigger fire off an xml message that contains the data to the BAM ADC webservice. The BAM ADC web service is http://server:port/OracleBAM/Services/DataObject/DataObjectOperations.asmx.
It has documentation on how to use it. I don't know if you're db can execute application code or not though.

Error - JMS Adapter in BPEL ..

We are trying to send the message to remote weblogic JMS Queue using JMS Adapter in BPEL, during that time we are getting the below error in our BPEL console, can anyone help us to solve this error?
Invoke_1 (faulted)
[2007/10/22 09:29:58] Faulted while invoking operation "Produce_Message" on provider "JMS_Demo".less
-<messages>
-<input>
-<Invoke_1_Produce_Message_InputVariable>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="opaque">
<opaqueElement xmlns="http://xmlns.oracle.com/pcbpel/adapter/opaque/">
Hello WIPRO
</opaqueElement>
</part>
</Invoke_1_Produce_Message_InputVariable>
</input>
-<fault>
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>
null
</code>
</part>
-<part name="summary">
<summary>
file:/C:/product/10.1.3.1/OracleAS_2/bpel/domains/default/tmp/.bpel_BPELProcess1_1.5_cb5d57e810459b549d857161eefb49f0.tmp/JMS_Demo.wsdl [ Produce_Message_ptt::Produce_Message(opaque) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
; nested exception is:
     ORABPEL-12167
ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
Please examine the log file to determine the problem.
</summary>
</part>
-<part name="detail">
<detail>
null
</detail>
</part>
</remoteFault>
</fault>
</messages>
[2007/10/22 09:29:58] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. More...
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>
null
</code>
</part>
-<part name="summary">
<summary>
file:/C:/product/10.1.3.1/OracleAS_2/bpel/domains/default/tmp/.bpel_BPELProcess1_1.5_cb5d57e810459b549d857161eefb49f0.tmp/JMS_Demo.wsdl [ Produce_Message_ptt::Produce_Message(opaque) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
; nested exception is:
     ORABPEL-12167
ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
Please examine the log file to determine the problem.
</summary>
</part>
-<part name="detail">
<detail>
null
</detail>
</part>
</remoteFault>

I got he same error but it's kind weird.
when I rebuild and deployed the jar,the error changes.
I have tested the remote jms queue and topic with java client. they are working fine.
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="summary"><summary>file:/home/bpel/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_Queue2Topic_v2007_12_10__37928_c62fd67a4741626244d92a80798b5d2c.tmp/OutTopicService.wsdl [ Produce_Message_ptt::Produce_Message(ExpenseRecord) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
file:/home/bpel/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_Queue2Topic_v2007_12_10__37928_c62fd67a4741626244d92a80798b5d2c.tmp/OutTopicService.wsdl [ Produce_Message_ptt::Produce_Message(ExpenseRecord) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor VIMConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
Please examine the log file to determine the problem.
[Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
; nested exception is:
     ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
file:/home/bpel/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_Queue2Topic_v2007_12_10__37928_c62fd67a4741626244d92a80798b5d2c.tmp/OutTopicService.wsdl [ Produce_Message_ptt::Produce_Message(ExpenseRecord) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor VIMConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
Please examine the log file to determine the problem.
[Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
</summary>
</part><part name="detail"><detail>null</detail>
</part></remoteFault>
Message was edited by:
user593125
Message was edited by:
user593125

Error in JMS adapter 11g

Hi
I have configured a JMS Adapter in Jdev 11.1.1.3.0 to consume message from a queue(JNDI Name as eis/wljms/WLQueue) on a weblogic server(10.3.1) in a different domain and deployed my BPM process to the soa server 11g.
I created a new outbound connection pool (eis/wljms/WLQueue) in Deployments->JMSAdapter->Configuration->Outbound Connection Pools with Connection Pool Interface: oracle.tip.adapter.jms.IJmsConnectionFactory
Also updated the factory properties field for eis/wljms/WLQueue with :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.75.85.151:9021;java.naming.security.principal=weblogic;java.naming.security.credentials=weblogic
And finally updated the deployment plan for JMSAdapter.
However I am getting the following error :
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample JMSMessageConsumer_init: Retrying connection; attempt #1>
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample
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 neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:207)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnec
tionFactory(JMSConnectionFactoryFactory.java:86)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:173)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.Sec
urityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialCo
ntextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
67)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.ja
va:183)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:131)
... 26 more
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticat
ed.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServi
ceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Sou
rce)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.jav
a:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173
Anyone has come across this issue? if yes, how do I resolve this?
Thanks

Have you tried cross-domain security or domain trust?

Error in Inbound JMS adapter(in ESB project)

Hello all,
I am trying out a sample ESB application, where an ESB service is listening on a JMS topic (OEMS database persistence) for new employee notifications. Upon receiving the message, the service will invoke a stored procedure to insert a record in the database.
I am using inbound jms adapter to receive the jms messages from a jms topic, that is configured using Oracle AQ. I made all the necessary changes in oc4j-ra.xml, application.xml, and data-sources.xml files.
But when I send a jms messages, I see the following errors in the oc4j log.xml:
Failed to activate endpoint for Service "DefaultSystem.AQJMStoDB.ListenForNewEmployees". Reason : oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: An unhandled exception has been thrown in the ESB system. The exception reported is: "ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter was unable to activate the endpoint :{} due to the following reason: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
[Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please correct the reported issue and redeploy the BPEL process.
     at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:566)
     at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateInboundJcaEndpoint(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.performEndpointActivation(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateEndpoint(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateEndpoint(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateService(Unknown Source)
     at oracle.tip.esb.server.service.EsbServiceFactory.activateEsbService(Unknown Source)
     at oracle.tip.esb.server.service.EsbServiceFactory.initializeEsbServices(Unknown Source)
     at oracle.tip.esb.server.common.RuntimeESBSystem.start(Unknown Source)
     at oracle.tip.esb.common.system.SystemFactory.startSystemsForCluster(Unknown Source)
     at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListenersForSystems(Unknown Source)
     at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListeners(Unknown Source)
     at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.startESBListeners(Unknown Source)
     at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.setupRuntime(Unknown Source)
     at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.initializeESB(Unknown Source)
     at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter$PingTester.run(Unknown Source)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
Caused by: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
     at oracle.tip.adapter.fw.wsdl.WSDLUtils.invokeSetMethod(WSDLUtils.java:763)
     at oracle.tip.adapter.fw.wsdl.WSDLUtils.setCciSpecParameters(WSDLUtils.java:665)
     at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:465)
     at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:421)
     at oracle.tip.adapter.fw.jca.AdapterLocator.findResourceAdapter(AdapterLocator.java:195)
     at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:341)
     ... 20 more
Can anybody provide any inputs on this error?
Thanks,
Pram

All,
Problem is solved. I changed the value for the Source directory & the adapter started to poll.
Thanx,
Homiar.

Error in Inbound JMS adapter (ESB project)

Hello all,
I am trying out a sample ESB application, where an ESB service is listening on a JMS topic (OEMS database persistence) for new employee notifications. Upon receiving the message, the service will invoke a stored procedure to insert a record in the database.
I am using inbound jms adapter to receive the jms messages from a jms topic, that is configured using Oracle AQ. I made all the necessary changes in oc4j-ra.xml, application.xml, and data-sources.xml files.
But when I send a jms messages, I see the following errors in the oc4j log.xml:
Failed to activate endpoint for Service "DefaultSystem.AQJMStoDB.ListenForNewEmployees". Reason : oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: An unhandled exception has been thrown in the ESB system. The exception reported is: "ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter was unable to activate the endpoint :{} due to the following reason: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
[Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please correct the reported issue and redeploy the BPEL process.
at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:566)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateInboundJcaEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.performEndpointActivation(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateService(Unknown Source)
at oracle.tip.esb.server.service.EsbServiceFactory.activateEsbService(Unknown Source)
at oracle.tip.esb.server.service.EsbServiceFactory.initializeEsbServices(Unknown Source)
at oracle.tip.esb.server.common.RuntimeESBSystem.start(Unknown Source)
at oracle.tip.esb.common.system.SystemFactory.startSystemsForCluster(Unknown Source)
at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListenersForSystems(Unknown Source)
at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListeners(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.startESBListeners(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.setupRuntime(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.initializeESB(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter$PingTester.run(Unknown Source)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
at oracle.tip.adapter.fw.wsdl.WSDLUtils.invokeSetMethod(WSDLUtils.java:763)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setCciSpecParameters(WSDLUtils.java:665)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:465)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:421)
at oracle.tip.adapter.fw.jca.AdapterLocator.findResourceAdapter(AdapterLocator.java:195)
at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:341)
... 20 more
Can anybody provide any inputs on this error?
Thanks,
Pram

All,
Problem is solved. I changed the value for the Source directory & the adapter started to poll.
Thanx,
Homiar.

JMS Adapter Native Correlation

Hello,
I've been trying to develop a request/reply service using JMS Adapter.
I Followed the steps in the "Adapter Knowledge Base: Technical Note #006: Correlation of Adapter messages within a BPEL process" document.
This document explains how to use the native correlation in the JMS Adapter by modifing the wsdl produced by the JMS Adapter Wizzard.
One of the thing the document says is that the invoke and recive must be sequencial and that the JMSMessageId of the first message should be placed in the JMSCorrelationId of the response.
I've done all the steps and developed a Message Driven Bean that reads the request and publishes the response accordingly.
I'm gessing that someone else already have this kind of problems...
If there is someone that might be able to help please send me an email to [email protected], so i can send the project to you.
Tks.

sorry, i forgot the say one thing.....
There is a table in the orabpel that is named Native_correlation....
somehow this table is never populated...
Tks once more

Weblogic.transaction.internal.TimedOutException while JMS adapter De queuing

Hi ,
I am getting the weblogic.transaction.internal.TimedOutException in SOA logs, when i track the instance using ecid. I am unable to find the flow in EM.
EM shows that instance as complete and I can able to see only the JMS adapter in flow trace.
Increasing the timeout is not a good option, I hope. It’s already set to 10800.
Error msg:
Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 10798
I am not sure y the De queuing take such a long time?? Any other thought guys??
Regards,
Ram.

Could you check the size of the JMS message that is getting polled.
When the transaction is getting rolled back, is the JMS message getting discarded or present in JMS Queue

JMS Adapter in BPEL 11g

Hi All,
i am trying to produce message to JMS QUEUE with the help of JMS Adapter.
PFB the Details:
jmsmodule:- NewJMSModule
Connection Factory :- jms/newconfactor
Queue jms/testqueue
create
oracle.tip.adapter.jms.IJmsConnectionFactory :- eis/jms/ajayQueue
provide location :- jms/newconfactor
I am getting below error
when my jms server target to AdminServer
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. JMSProject:JMSQueueInsertion [ Produce_Message_ptt::Produce_Message(body) ] : 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 eis/confac 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.
when my jms server target to SoaServer
<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: ERRJMS_ERR_CR_QUEUE_PROD. ERRJMS_ERR_CR_QUEUE_PROD. Unable to create Queue producer due to JMSException. Please examine the log file to determine the problem. ". 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>[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.</detail>
Any help is appreciated.
Regards,
Ajay

Hi Ajay,
It seems that your SCA is looking for a connection factory with the JNDI name "eis/confac" instead of "eis/jms/ajayQueue" which is the one you configured. You should have a "*_jms.jca" file in your project with the following entry: <connection-factory location=" .. . Could you check that it is pointing to the correct JNDI
best regards, Nicolas

Having multiple service operations in a single JMS adapter best practice

Hi All,
I am using JDeveloper and SOA Suite 11.1.1.6. I need to read from multiple JMS Topics and transform and enhance the messages through the Mediator and then persist into Database.
My question is
What is the best practice to consume from multiple topics, Should I configure separate JMS adapter for each of the Topic destination
OR
have a single JMS adapter with multiple operations by manually changing the JMS adapter wsdl and jca file?
I find cannot have
Please suggest.
Thanks in advance
Edited by: user5108636 on 15/05/2013 11:36

Hi Vijay,
did you actually test this? When I finish creating a DBAdapter, there is a operation present. Then when I click edit again on the DBAdapter, and I create another select, when I finish only the first operation is gone, and I can only see the one I've created via the last edit.
I dont understand your reply. Can I have two operations, each one with select underneath, in the same adapter?
Edited by: user13604541 on Jan 30, 2012 11:19 AM

Calling Foreign JMS in SOA Suite 11g JMS Adapter

Hi,
Just want to get some guidance in the implementation of Foreign JMS in WebLogic 10.3.
I followed the creation of the Foreign JMS Server using this document:
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignServers.html
I am trying to connect to a remote Weblogic 10.3 JMS queue but cannot get pass the JDev wizard stage.
I need to call the foreign JMS via the Fusion 11g JMS Adapter but cannot lookup the destination from the JDev wizard. My composite will produce a message that will end up in the remote queue.
Has anybody got this to work? Is this supported in JMS Adapter? I've read quite a few using MDB to call the Foreign JMS but not JMS Adapter.
Regards,
Robert

Please refer to the following document that shows how to access remote wls jms queues and topics. This is the preferred way when accessing remote wls destinations.
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
Thanks
Aman

Invoking Jms Adapter from BPEL with enque stoped

Hi guys, I have an issue.
In my BPEL flowI have an invoke activity which has a jms adapter as a partner link.
The thing is that if you stop the enque in the DB, your flow in BPEL continues like nothing happened. It just passes the payload to the jms adapter. From it's point of view is asynchronous , but I want to make sure that the payload is in the queue before I continue the flow.
Any ideas?

Hi Oracler,
I don't understand what you mean by XML schema inline? Where do you define that in a JMS adapter ? Can you be more specfic when you say Try including both the elements(TEXT_LOB , TEXT_VC ) in the schema? I don't have those elements in my schema at all. I have tried the opaque option I still get the same Translator NULL error.
Please anyone help....

Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ

Hello
I am trying to send some msg from Http client
I configured JMS adapter as receiver
Transport Protocol :WEBsphereMQ JMS provider
Message protocol :JMS1.x
I have given the Ip address of my machine where I installed WEB Sphere MQ
Server Port :1416
Transport Protocol :WebSphere MQ
JMS compliant: JMS-compliant
In SXMB_MONI
Http client sends message without any error.
But while tracing I got message
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
Can anybody tell me the solution..
Thnaks

Hi,
I have not directly faced this but i may suggest ,
1. What do you see in sxmb_moni, do you have a queue problem?
2. see this File-to-File Scenario Stopped Working the reply from Shravan and the last message.
<i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Anirban.

ORABPEL-12141 JMS Adapter

Similar Messages

Maybe you are looking for