Oracle-JMS (OJMS) to WebSphereMQ-JMS Propagation...

Has any body accomplished this? For example, a propagation where the Oracle AQ queue table payload on the Oracle side is one of the JMS types (e.g SYS.AQ$_JMS_MESSAGE) and the message link for the DBMS_MGWADM.CREATE_MSGSYSTEM_LINK call is created with either DBMS_MGWADM.JMS_CONNECTION interface or the DBMS_MGWADM.JMS_QUEUE_CONNECTION interface. Of course, that message link is pointing to a WebSphereMQ queue manager and WebSphereMQ outbound log queue.
Any help is appreciated. I've submitted a response to Oracle support on Metalink and it's been almost three days and still no response. Also, I've been using the Messaging gateway for non-JMS propagation for a long time now and that works fine. In other words, the queue table payload is SYS.MGW_BASIC_MSG_T and the message link is created with the DBMS_MGWADM.MQSERIES_BASE_JAVA_INTERFACE interface. Something about making it pure JMS on the message exchange isn't working out for me.
blake

Hey Phillip,
I think to solve your first problem the following might work.
1. Open DBA Studio, login as SYS.
2. Open 'Security' tab for your database.
3. Click the entry for the user's schema that you are running your Java code in.
4. Click 'Object Privileges' tab.
5. Open 'SYS|Packages'
6. Click on 'DBMS_AQADM_SYS'
7. Click on the word 'EXECUTE' in the right-hand pane.
8. Click the down arrow to add the privilege.
9. Click 'APPLY'
If you get a message stating insufficient privileges then maybe you need to logon to your OS as a member of the SYSDBA group.
This is with the Oracle 8i DBA Studio client BTW, I don't know squat about 9i (or really 8i for that matter).
Hope it helps

Similar Messages

  • Queue using OracleAS JMS

    hi , we have developed an application where we have a queue in websphere MQ and the application server used is oracle 10g . Now instead of using the websphereMQ or any other third party software , can we create a a queue and queue manager(MQ terminology ) in the oracle application server. We have created the queue destination and the connection factory in the oarcle , but how actully we have to create a queue and queue manger or is it not necessary to make one or is there any other way around, and we are trying for OEMS JMS In-Memory and File-Based Persistence , and hopefully the xml files are in right place i was refering to http://download-east.oracle.com/docs/cd/B25221_04/web.1013/b14427/jms.htm#sthref141
    for the development

    That's the right doc, you should create your destination and connection factory in jms.xml which is in j2ee/home/config directory.
    Here contains howto for using OracleAS JMS in 10.1.3:
    http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html#JMS
    http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-connect-to-oemsjmsmf/doc/how-to-connect-to-oemsjmsmf.html
    -Frances

  • Oracle JMS Advanced Queuing

    Problems with Oracle JMS Advanced Queuing
    Hello,
    We have build an application using Advanced Queuing (database version 10.2.0.1.0). Everything works fine using PL/SQL. But when we try to send in messages through the Oracle JMS interface messages with less then 4000 bytes are stored in the queu table but the content of the message is not stored in one of the user data attributes.
    Messages larger then 4000 bytes result in the following error:
    oracle.jms.AQjmsException: JMS-204: Er is een fout opgetreden in de AQ JNI-laag.
    at oracle.jms.AQjmsError.throwEx(AQjmsError.java:311)
    at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1323)
    at oracle.jms.AQjmsProducer.send(AQjmsProducer.java:692)
    at oracle.jms.AQjmsProducer.send(AQjmsProducer.java:465)
    at nl.detailresult.aqadapter.test.OracleQueueSendTextMsgTest.testOracleQueuePlus4000(OracleQueueSendTextMsgTest.java:125)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at junit.framework.TestCase.runTest(TestCase.java:154)
    at junit.framework.TestCase.runBare(TestCase.java:127)
    at junit.framework.TestResult$1.protect(TestResult.java:106)
    at junit.framework.TestResult.runProtected(TestResult.java:124)
    at junit.framework.TestResult.run(TestResult.java:109)
    at junit.framework.TestCase.run(TestCase.java:118)
    at junit.framework.TestSuite.runTest(TestSuite.java:208)
    at junit.framework.TestSuite.run(TestSuite.java:203)
    at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
    [Linked-exception]
    oracle.jms.AQjmsException: ORA-00942: table or view does not exist
    As far as I can see we have done everything according to the books but does anyone have a clue what we might have missed?

    Hi,
    Have you found a solution to this? I am running into similar issue with SOA Suite using OJMS queues.
    Regards,
    Rajesh

  • Error initializing the Oracle JMS Resource provider for Topics

    Getting this error when starting OC4J 9.0.3 standlone on Windows2000.
    Resource provider config'd as
    <resource-provider class="oracle.jms.OjmsContext" name="ojms">
    <description> OJMS/AQ </description>
    <property name="datasource" value="jdbc/ProlianceDS"></property>
    </resource-provider>
    Datasource config'd as
         <data-source
              class="com.evermind.sql.OrionCMTDataSource"
              name="ProlianceDS"
              location="jdbc/ProlianceDS"
              xa-location="jdbc/xa/ProlianceDS"
              ejb-location="jdbc/ProlianceDS"
              connection-driver="oracle.jdbc.driver.OracleDriver"
              username="proliance"
              password="******"
              url="jdbc:oracle:thin:@aps67.ere.com:1538:ifstst"
              inactivity-timeout="30"
         />
    ejb-jar config'd as
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <enterprise-beans>
    <message-driven>
    <description>Proliance Message Driven Bean</description>
    <display-name>ProlianceMDB</display-name>
    <ejb-name>ProlianceMDB</ejb-name>
    <ejb-class>com.lendlease.bll.ProlianceMDB</ejb-class>
    <transaction-type>Container</transaction-type>
    <message-selector>
    <method>
    <ejb-name>ProlianceMDB</ejb-name>
    <method-name>onMessage</method-name>
    </method>
    </message-selector>
    <message-driven-destination>
    <destination-type>javax.jms.Topic</destination-type>
    <subscription-durability>Durable</subscription-durability>
    </message-driven-destination>
    <resource-ref>
    <res-ref-name>java:comp/resource/ojms/Topics/PROLIANCE.OUT_AQ</res-ref-name>
    <res-type>javax.jms.Topic</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>java:comp/resource/ojms/TopicConnectionFactories/aqTcf</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.TopicConnectionFactory</resource-env-ref-type>
    </resource-env-ref>
    </message-driven>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>ProlianceMDB</ejb-name>
    <method-name>onMessage</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    orion-ejb-jar config'd as:
    <?xml version = '1.0'?>
    <!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
    <orion-ejb-jar deployment-time="e7f1ce76f6" deployment-version="1.0.2.2">
    <enterprise-beans>
    <message-driven-deployment
    name="ProlianceMDB"
    connection-factory-location="java:comp/resource/ojms/TopicConnectionFactories/aqTcf"
    destination-location="java:comp/resource/ojms/Topics/PROLIANCE.OUT_AQ"
    subscription-name="PROLIANCE_SUBSCRIBER">
    </message-driven-deployment>
    </enterprise-beans>
    </orion-ejb-jar>
    Full startup trace is:
    C:\ora\oc4j_9.0.3\j2ee\home>java -Djdbc.connection.debug=true -jar oc4j.jar
    Node started with id=-2143203582
    Auto-unpacking C:\ora\oc4j_9.0.3\j2ee\home\applications\ProlianceMDB.ear... done.
    Auto-unpacking C:\ora\oc4j_9.0.3\j2ee\home\applications\ProlianceMDB\ProlianceMDB.war... done.
    Auto-deploying ProlianceMDB (New server version detected)...
    Copying default deployment descriptor from archive at C:\ora\oc4j_9.0.3\j2ee\home\applications\ProlianceMDB/ProlianceMDB
    .jar/META-INF/orion-ejb-jar.xml to deployment directory C:\ora\oc4j_9.0.3\j2ee\home\application-deployments\ProlianceMDB
    \ProlianceMDB.jar...
    Auto-deploying ProlianceMDB.jar (New server version detected)... done.
    Error initializing the Oracle JMS Resource provider for Topics: Not an OracleConnection
    Error deploying file:/C:/ora/oc4j_9.0.3/j2ee/home/applications/ProlianceMDB/ProlianceMDB.jar homes: No javax.jms.Destina
    tion found at the specified destination-location (java:comp/resource/ojms/Topics/PROLIANCE.OUT_AQ) for MessageDrivenBean
    ProlianceMDB
    OrionCMTConnection not closed, check your code!
    Logical connection not closed, check your code!
    Created at:
    java.lang.Throwable: OrionCMTConnection created
    at com.evermind.sql.OrionCMTConnection.<init>(OrionCMTConnection.java:42)
    at com.evermind.sql.OrionCMTDataSource.getConnection(OrionCMTDataSource.java:82)
    at oracle.jms.AQjmsConnection.newDBConnection(AQjmsConnection.java:1681)
    at oracle.jms.AQjmsConnection.<init>(AQjmsConnection.java:537)
    at oracle.jms.AQjmsTopicConnectionFactory.createTopicConnection(AQjmsTopicConnectionFactory.java:232)
    at oracle.jms.OjmsResource.initT(OjmsResource.java:512)
    at oracle.jms.OjmsResource.initAQ(OjmsResource.java:411)
    at oracle.jms.OjmsResource.init(OjmsResource.java:214)
    at oracle.jms.OjmsContextFactory.getObjectInstance(OjmsContextFactory.java:103)
    at oracle.jms.OjmsContext.getResource(OjmsContext.java:328)
    at com.evermind.server.Application.lookupResource(Application.java:2548)
    at com.evermind.server.Application.lookupResource(Application.java:2563)
    at com.evermind.server.ApplicationContext.handleResourceLookup(ApplicationContext.java:639)
    at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:162)
    at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:66)
    at com.evermind.server.ejb.MessageDrivenHome.<init>(MessageDrivenHome.java:236)
    at com.evermind.server.ejb.EJBPackageDeployment.bindHomes(EJBPackageDeployment.java:304)
    at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:595)
    at com.evermind.server.Application.postInit(Application.java:431)
    at com.evermind.server.Application.setConfig(Application.java:136)
    at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1635)
    at com.evermind.server.ApplicationServer.initializeApplications(ApplicationServer.java:1585)
    at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1240)
    at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
    at java.lang.Thread.run(Thread.java:484)
    Auto-deploying ProlianceMDB Poster (New server version detected)...
    Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized
    Using native aqapi.jar with OC4J -didn't copy from 9.2.0.2 DB. 9.2.0.2 patchset ran fully, completed fine. What's going wrong?
    Brian

    Shouldn't I be getting a com.evermind.sql.OrclCMTConnection created instead of a com.evermind.sql.OrionCMTConnection (per the stack trace)? OJMS is complaining that it doesn't have an OracleCOnnection but how do I tell it to use the "OrclCMTConnection" class instead?
    Brian

  • Oracle.jms.AQjmsException when inserting large MessageMap message via JMS

    Is there a limit on the number of items/size of message that can be placed on the AQ using the MessageMap message format?
    Ive attempted to place 100 elements, each a small string of approximately 20 characters, into the AQ but I get the following error.
    ---> nested oracle.jms.AQjmsException: JMS-204: An error occurred in the AQ JNI layer
    If I reduce the number of elements to about 70 the message is successfully queued.

    As long as the byte array obtained by serializing the JMSMapMessage
    java object instance fits in a BLOB (max size 4 Gig) you should be able to
    enqueue your message (providing the OS and/or the JVM can handle it).
    Smaller map messages are stored inline in the table itself. Larger messages
    are stored in a BLOB. It is likely that you do not have permissions to
    write to the BLOB field of the OJMS MapMessage ADT.
    To figure out the exact SQL exception turn tracing on by putting the following
    lines of code in your OJMS client and recompiling.
    AQjmsOracleDebug.setDebug(true);
    AQjmsOracleDebug.setTraceLevel(5);
    This will give you the exact SQL exception that is thrown.
    -Vivek

  • Create EJB 3.0 Message Driven Bean on a Oracle JMS (AQ)

    Hi, I need to develop a EJB 3.0 Message Driven Bean. The MDB has to work on a Oracle AQ using Oracle JMS. Is there any how-to document giving an example about this issue. Can you give an example how to create the JMS destination in OC4J (how to configure the Oracle JMS AQ in OC4j), issue the JMS destination via annotions (resource injection) in the MDB. Please give me a working example of the MDB and a test client to produce a message. Regards, Arjan Jorritsma

    Check your ejb-jar.xml and see if it has the version of "2.1" there...
    If the application was depending upon EJB 3.0 annotations but it had a ejb-jar.xml that had version set to "2.1" and there was no oracle specific descriptor (orion-ejb-jar.xml) to designate it use the resource adapter; It would expect JMS destination and connection factory that is required for a JMS-MDB set in the ejb-jar.xml. So try to change the ejb-jar.xml to update the version to "3.0", OC4J would have parsed the annotation and combined the metadata with ejb-jar.xml and it would work.
    -Frances

  • Oracle.jms.AQjmsException: Error creating the db_connection( OSB PS2.)

    hi All,
    I am beginner in OSB 11g. Please excuse me if I am asking any dumb question.
    I am trying to post messages to Oracle AQ by configuring JMS Destination in OSB Alert destination
    I have configured AQ JMS in weblogic 10.3.3 ( OSB PS2) following the blog (http://jianmingli.com/wp/?p=2950)
    When i invoked my proxy OSB proxy service i am getting following exception. Can you please help if i am missing any kind of setup while configuring the JMS Module.
    Caused By: oracle.jms.AQjmsException: Error creating the db_connection
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:625)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.getSession(JmsOutboundMessageContext.java:399)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.newMessage(JmsOutboundMessageContext.java:621)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.setRequestMetaData(JmsOutboundMessageContext.java:229)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.access$100(JmsOutboundMessageContext.java:72)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:788)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:551)
         at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:680)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy111.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:489)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
         at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
         at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:345)
         at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
         at com.bea.alsb.alert.pipeline.PipelineAlertManager.processAlert(PipelineAlertManager.java:59)
         at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:125)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:102)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
         at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
         at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
         at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
         at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
         at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
         at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)

    hi All,
    Here is the actual exception while posting message into AQ ( AQ JMS) from OSB.
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
    at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
    at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
    Not sure what is missing in my AQ JMS configuration. Please help.
    Regards,
    Nagi

  • How to configure global transaction wthin Oracle AS JMS and Oracle JMS

    How to configure global transaction if I take a message from Oracle JMS(AQ) and send it to the Oracle JMS?

    Which version of OC4J are you working on?
    In OC4J 10.1.3.x, presume your OC4J JMS listens messages via MDB which uses a resource adapter as a message listener. The resouce adaper could be the generic JMS adapter deployed in OC4J as the default.
    Resource adapter configuration to support MDBs is included in the standard ra.xml file, which lists the message listener types that the resource adapter supports.
    The MDB developer or deployer configures the MDB in the ejb-jar.xml file, through a <message-driven> element.
    In addition to above, configuration in the ejb-jar.xml file specifies whether an MDB uses transactions.
    1) The <transaction-type> subelement of <message-driven> in ejb-jar.xml has a value of Container, and the <trans-attribute> subelement of <container-transaction> (under the <assembly-descriptor> element) has a value of Required. In this circumstance, if there is an imported transaction, then message delivery and related work are performed within that transaction. If there is no imported transaction, OC4J creates a transaction, and message delivery and related work are performed within that transaction.
    2) The <transaction-type> subelement of <message-driven> in ejb-jar.xml has a value of Bean. In this circumstance, the MDB manages the transaction. If a transaction is imported, OC4J will suspend it before the message delivery method call to the MDB, in order to avoid conflict.
    Message delivery is not transacted if the <transaction-type> subelement of <message-driven> in ejb-jar.xml has a value of Container, but the <trans-attribute> element has a value of NotSupported. If there is an imported transaction in this circumstance, OC4J will suspend the transaction before the message delivery method call to the MDB.
    Details could be found from OC4J Resource Adapter Guide.

  • Weblogic Connection with Oracle JMS AQ errors

    Hi All,
    I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
    The steps I followed exactly are this :
    1) Created a Database Queue called DemoInqueue using the following scripts :
    exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
    COMMIT;
    exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
    COMMIT;
    exec dbms_aqadm.start_queue('DemoInQueue');
    COMMIT;
    2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
    3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
    Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
    Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
    QAConnectionFactory but no difference )
    Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
    4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
    operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
    populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
    are the same....
    Are these steps correct ? Am I missing something here.?
    I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
    Here is the error stack below :
    <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "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 aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    ####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "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 aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    SOA LOG.....
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
    oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
    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.
    HelloWorldComposite:Publishmessage [ 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 aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.

    Thanks for passing along the link.
    The part about Oracle's documentation not mentioning the JmsAdapter configuration was a real sticking point for me - I was having the same problem as the original poster until I updated that deployment as the link outlined.
    Also, towards the end of that link the author mentions running in to problems getting their composite to successfully bind to the queue definitions that were created in WebLogic.
    I attempted post my solution to this on the original site, but I'm not sure if it got through - so I'll add the details of what worked for me here:
    Connection Factory:
    Local JNDI: aqjms/JMSTest_Connection_Factory
    Remote JNDI: XAQueueConnectionFactory
    Destination:
    Local JNDI: aqjms/JMSTest_Queue
    Remote JNDI: Queues/JMSTest_Queue
    Outbound Connection Pool:
    Name: eis/aqjms/JMSTest_Queue
    Connection Factory: aqjms/JMSTest_Connection_Factory
    JDeveloper Composite:
    Destination Name: aqjms/JMSTest_Queue
    JNDI Name: eis/aqjms/JMSTest_Queue
    Cheers,
    - Nathan

  • Oracle.jms.AQjmsException: invalid arguments in call

    Hi
    Has anyone seen this error before?
    Environment Configuration:
    APP SERVER 9.0.4 (OUT 0F BOX CONFIG)
    JDK 1.4
    RED HAT ENTERPRISE SERVER 3.0
    COMPAC DL380
    ON VM SOFTWARE
    DB 9.2.0.4
    HP-UX 11i
    SUPERDOME
    Error logs:
    [18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.common.jms.pool.QueueConnectionPool]
    [getQueueConnection] :Using pooled queue connection for factory:
    java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB
    [18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.common.jms.pool.QueueSessionPool]
    [createQueueSession] :Failed to create queue session: oracle.jms.AQjmsException: invalid arguments in call
    [18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.common.jms.BytesMessageWriter]
    [writeBytesMessage] :Failed to write message onto queue: java:comp/resource/SDEJMS/Queues/SDEDEV_LOGQUEUE using queue
    factory: java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB - bcc.sde.common.jms.pool.JMSPoolException:
    QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments in call
    [18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.sil.common.log.silInteractionLogger] [log]
    :silInteractionLogger.log() Exception writing ServiceExecutionRecord to JMS queue: bcc.sde.common.exception.SDEException:
    Failed to write message onto queue: java:comp/resource/SDEJMS/Queues/SDEDEV_LOGQUEUE using queue factory:
    java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB - bcc.sde.common.jms.pool.JMSPoolException:
    QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments in
    call: QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments
    in call;
    ---> nested: bcc.sde.common.jms.pool.JMSPoolException: QueueSessionPool.createQueueSession() failed to create queue
    session - oracle.jms.AQjmsException: invalid arguments in call
    [18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.sil.bids.api.sql.BidsSQLInterface]
    [logInteractionRecord] :Failed to log interaction record: bcc.sde.common.exception.SDEException: silInteractionLogger.log()
    Exception writing ServiceExecutionRecord to JMS queue: bcc.sde.common.exception.SDEException: Failed to write message onto
    queue: java:comp/resource/SDEJMS/Queues/SDEDEV_LOGQUEUE using queue factory:
    java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB - bcc.sde.common.jms.pool.JMSPoolException:
    QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments in
    call: QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments
    in call;
    ---> nested: bcc.sde.common.jms.pool.JMSPoolException: QueueSessionPool.createQueueSession() failed to create queue
    session - oracle.jms.AQjmsException: invalid arguments in call
    Database error with same error message:
    ORA-17433 - invalid arguments in call
    http://www.doc.gold.ac.uk/oracle/doc/java.817/a83724/ermesap3.htm
    Code causing problem:
    queueConnection = queueConnectionPool.getQueueConnection(queueConnectionFactoryName, runningExternal);
    queueSession = queueConnection.createQueueSession(TRANSACTIONAL, AUTO_ACK_MODE);

    I am facing the same problem. Have you figured out what the cause was? Thanks,

  • JMS Enqueue/Dequeue without using oracle.jms package

    Hi,
    Is it possible to successfully enqueue/dequeue messages from Oracle AQ using JMS which only uses the classes under javax.jms package, not the classes under oracle.jms package. If possible, can anybody please provide some step by step example.
    Thanks

    You can get the connection factory and the queue from an application server's jndi. Create a resource provider reference in oc4j and get them from there. Read the oc4j services guide, oems (jms) chapter for how to do that.
    I think if you are not using an application server you can also get the connection factory and queue from an ldap directory. check out Aq user guide for that.

  • Oracle JMS using AQ throwing InvalidDestinationException

    While creating Queue(AQJMS) using Application-Client.xml as shown below iam getting the below shown error. I have configured the Oracle JMS Provider and datasource on Server . Can you Please suggest me what has to be done. Iam using Oracle 10g AS(10.1.2).
    Error
    javax.jms.InvalidDestinationException: Destination "JMSUSER.demoQueue" has inval id type "class oracle.jms.AQjmsDestination" and cannot be used with OC4J JMS.
    at com.evermind.server.jms.EvermindDestination.checkDestination EvermindDestination.java:262)
    at com.evermind.server.jms.EvermindMessageProducer.<init>(EvermindMessageProducer.java:61)
    at com.evermind.server.jms.EvermindQueueSender.<init>(EvermindQueueSender.java:50)
    at com.evermind.server.jms.EvermindQueueSession.createSender(EvermindQueueSession.java:91)
    at mypackage.Test.enqueue(Test.java:107)
    at mypackage.Test.<init>(Test.java:37)
    at mypackage.Test.main(Test.java:48)
    [application-client.xml]
    <resource-ref>
    <res-ref-name>jms/YourQueueConnectionFactory</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Application</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>jms/demoQueue</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    [orion-application-client.xml]
    <resource-ref-mapping
    name="jms/YourQueueConnectionFactory"
    location="java:comp/resource/OJMSReference/QueueConnectionFactories/someQcf" />
    <resource-env-ref-mapping name="jms/demoQueue" location="java:comp/resource/OJMSReference/Queues/jmsuser.demoQueue"/>
    Thanks in Advance for the help.

    no not required. Foreign JMS for Weblogic is independent of OSB. It will work with out installation of OSB.
    Manoj

  • Oracle JMS AQ connection using Weblogic 10.3.3

    Hi All,
    I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
    The steps I followed exactly are this :
    1) Created a Database Queue called DemoInqueue using the following scripts :
    exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
    COMMIT;
    exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
    COMMIT;
    exec dbms_aqadm.start_queue('DemoInQueue');
    COMMIT;
    2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
    3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
    Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
    Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
    QAConnectionFactory but no difference )
    Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
    4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
    operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
    populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
    are the same....
    Are these steps correct ? Am I missing something here.?
    I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
    Here is the error stack below :
    <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "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 aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    ####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "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 aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    SOA LOG.....
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
    oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
    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.
    HelloWorldComposite:Publishmessage [ 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 aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.

    I executed your scripts one by one and then tried again. Same Error Message. I think the problem is not in the AQ queue. The issue is with the BPEL / SOA process as the error message below clearly says it's not able to find aqjms/XAQueueConnectionFactory. That's the JNDI name in my Jdeveloper ? Is that JNDI what I should be using or should be match something else ? Please help................
    Latest Error LOG...
    <<anonymous>> <BEA1-0B06BE09987B4FFD1A5C> <3f3d2d8955322f32:-73cb8b9a:12ca58d835d:-7fd3-0000000000000123> <1291268540004> <BEA-000000> <<CubeEngine::handleWorkItem> This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. Root cause : com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
    parts: {{
    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.
    HelloWorldComposite:Publishmessage [ 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 aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    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>
    ,detail=<detail>aqjms/XAQueueConnectionFactory</detail>
    ,code=<code>null</code>}
    >

  • Orion JMS Vs Oracle JMS

    Hi
    I am deploying an application with MDB using Oracle JMS( AQ ) and durable subscriptions. Now for configuration of the topics, I have a doubt. In addition to creation of the topics in the db do I have to specify those in jms.xml or it is required only in case of Orion JMS? I am really confused with this, since I am getting a deployment error even though I have configured orion-ejb-jar.xml as per AQ req... Any help pls...
    Thanks in Advance...

    Hi Gilbert,
    I have done the same, but while deploying it gives error 'Syntax error in source' with no other error message. And I have one more doubt. Does AQ work with Oracle 8i databse ?

  • Putting messages direct to OracleAS JMS

    Hi Folks,
    I'm developing a .NET Application and I need to send messages to a destination(queue) in the Oracle Application Server using OracleAS JMS.
    Does anyone know how to do that?
    Thanks in advance,
    Patrick

    I don't think so. The interfaces are different. Java --> C# directly, how?
    Here is an example (googled) of using java webservices with .net, even the customer does not want to use web services. maybe others could comment on this.
    http://www.codeproject.com/cpnet/C__JavaWebServices_JMS.asp
    -Frances

Maybe you are looking for

  • How can I change the default Country for my account!!!

    Hi, I just move in to U.S. and i'm trying to use the U.S. store but the systems tells me tha my account it's only valid for Venezuela... What can I do??? thanksin advance  for any help!!!!

  • I just installed windows 7 and i get a hp quick launch compatibility issue warning? what can i do?

    Does this issue about my computer or printer?  

  • Ratio calculation issue

    Hello, i am stuck up in building a report thru Report Painter from GRR1. The report involves ratio calculation like debt-equity, RONW, etc.. In the Lead column, i have put various selection parameters like Fiscal Year, Co Code, Period etc which is wo

  • [iPhone] Back Button

    Is there a way to get the left pointed button style that back buttons use? I'm trying to put a back button on a custom view I created so just setting navigationItem.backBarButtonItem to a UIBarButtonItem doesn't work. It never appears. I need to set

  • Setting up an e-mail account

    Probably a dumb question, but I'm following the steps to set up a new e-mail account on the iTouch. I have entered my account information (user name, email addy, password). At this point I'm supposed to tap "Save". I cannot see anything marked "Save"