JMS Adapter: Disabling debug log

Hi All,
we are having trouble with the JMS Adapter. Adapter is showing message in the opmn/default oc4j intance log growing until 15gb or more..
Is there a way to disable the JMS transaction log ?
Log is showing the following lines:
<2010-02-25 13:12:48,244> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_start(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.04.74.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),0) invoked:oracle.tip.adapter.jms.JmsXAResource@121c9d1
<2010-02-25 13:12:48,267> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_end(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d5.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),67108864) invoked:oracle.tip.adapter.jms.JmsXAResource@be22d2
<2010-02-25 13:12:48,268> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_commit(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d5.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),true) invoked:oracle.tip.adapter.jms.JmsXAResource@be22d2
<2010-02-25 13:12:48,269> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_isSameRM(oracle.tip.adapter.jms.JmsXAResource@be22d2) invoked:oracle.tip.adapter.jms.JmsXAResource@be22d2
<2010-02-25 13:12:48,269> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_setTransactionTimeout(10800) invoked:oracle.tip.adapter.jms.JmsXAResource@16d2727
<2010-02-25 13:12:48,269> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_start(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.0b.74.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),0) invoked:oracle.tip.adapter.jms.JmsXAResource@16d2727
<2010-02-25 13:12:48,271> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_end(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d7.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),67108864) invoked:oracle.tip.adapter.jms.JmsXAResource@f03668
<2010-02-25 13:12:48,272> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_commit(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d7.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),true) invoked:oracle.tip.adapter.jms.JmsXAResource@f03668
<2010-02-25 13:12:48,273> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_isSameRM(oracle.tip.adapter.jms.JmsXAResource@f03668) invoked:oracle.tip.adapter.jms.JmsXAResource@f03668
<2010-02-25 13:12:48,273> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_setTransactionTimeout(10800) invoked:oracle.tip.adapter.jms.JmsXAResource@c99711
Thanks in advance.
Regards,
Marcelo.

In fact I think this is a BPEL question. The log level for default.collaxa.cube.ws is controlled from the BPEL console (at least before 11g, I bet it remains more or less the same).
In 10g you would log in to the BPEL console, select "Manage BPEL Domain", select "Logging" and then find the logger named "default.collaxa.cube.ws" in the list. Change the dropdown to a higher log level, for example Warn. Apply the changes and you are done. You may need to restart the instance if it doesn't seem to help.
I can't point to the exact screens in 11g as I don't have it here, but the general procedure should be the same. Good luck!

Similar Messages

  • How to read Java Object message from JMS Queue using JMS Adapter .

    Dear All,
    In my scenario i have to read a java object message from JMS Queue . I tried by using the JMS Adaper ,but i am not getting any Payload . Can any one tell me is there any special settings for JMS Adapter to read the Java Object message .
    I am able to read the Message successfully thru JMS Adapter but in SXMB_MONI it is not showing any payload .
    I also went in Message monitoring but i am getting this type of message in Sender JMS Adapter  in Audit Log.
    JMS Message ID XXXXX Message Type Null unknown.Payload can not be read and will be empty.
    JMS Message ID XXXXX Payload Empty can not read.
    Please Help.
    Lateef

    Hi,
    As far as i know, JMS Object Messages is not supported by XI JMS adapter.
    you need to have the JMS provider to transform the message to bytes messages.
    (Refer to SAP note 856346)

  • Debugging JMS adapter with Module Configuration

    Hi.
    I have a problem debugging my JMS adapter with module configuration.
    All I get from the Message Monitor is a status "System Error", and no error category or error message.
    I know there's an error in my Module configuration design, since it works fine without.
    My configuration looks like this:
    PROCESSING SEQUENCE:
    1     localejbs/AF_Modules/MessageTransformBean     Local Enterprise Bean     XML2Plain
    2     localejbs/SAP XI JMS Adapter/ConvertMessageToBinary     Local Enterprise Bean     convert_XI2Bin
    3     localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService     Local Enterprise Bean     exit
    MODULE CONFIGURATION:
    XML2Plain     Transform.Class     com.sap.aii.messaging.adapter.Conversion
    XML2Plain     Transform.ContentType     text/plain;charset=utf-8
    XML2Plain     xml.conversionType     StructXML2Plain
    XML2Plain     xml.addHeaderLine     0
    XML2Plain     xml.recordsetStructure     STARTRECORD,DATARECORD,SERVICEYDELSERRECORD,SLUTRECORD
    XML2Plain     xml.STARTRECORD.fieldFixedLengths     2,8,6,7,10,7,3,3
    XML2Plain     xml.DATARECORD.fieldFixedLengths     2,8,6,4,35,17,7,7,7,5,5,5,18,18,18,18,18,18,18,18,18,9
    XML2Plain     xml.SERVICEYDELSERRECORD.fieldFixedLengths     2,8,6,4,3,20,18,18,18
    XML2Plain     xml.SLUTRECORD.fieldFixedLengths     2,8,6,7,10,7
    XML2Plain     xml.STARTRECORD.fixedLengthTooShortHandling     Cut
    XML2Plain     xml.DATARECORD.fixedLengthTooShortHandling     Cut
    XML2Plain     xml.SERVICEYDELSERRECORD.fixedLengthTooShortHandling     Cut
    XML2Plain     xml.SLUTRECORD.fixedLengthTooShortHandling     Cut
    The structure of the message looks like this:
    <STARTRECORD> (occurence = 1)
    <DATARECORD> (occurence = 1..unbounded)
    --- <SERVICEYDELSERRECORD> (occurence = 0..unbounded)
    <SLUTRECORD> (occurence = 1)
    I've crosschecked every field, and it length and all looks like it should!
    The worst part is the one not getting the reason why it fails. Any way I can get this information?
    I've tried to look in the Adapter Framework log, but I have no clue where to look for anything usefull.
    Help
    Regards Peter

    Hello,
    Below is the module configuration in my JMS sender channel:
    Check Message          Local Enterprise Bean          key
    ConvertJMSMessageToBinary      Local Enterprise Bean      convert_JMS2Bin
    ConvertBinaryToXMBMessage     Local Enterprise Bean      convert_Bin2XI
    CallSapAdapter                Local Enterprise Bean          call_AF_MS
    CheckMessage is a custom module which does some check on the incoming message.
    Now what I want to know is at which position should I include the DynamicConfiguration Bean? Should it be included at position 1 or at position 2 or someother position?
    ~Thanks.

  • Error log on jms adapter

    Hi,
    I have an XI 3.0 connected to an MQ via jms adapter in an Adapter Engine
    I have this log when sending a message:
    15:39:18 (3130): JMS message ID:414d51204d51584944573120202020207a07c64442701b00 sent successfully
    15:39:18 (3140): Session commited
    15:39:18 (3180): Se produjo un error java.io.IOException: Error during rendering: Missing mandatory element <sap:queueId> for quality of service EOIO
    15:39:18 (3190): Session rolled back
    I'm trying to discover the mandatory element.
    Regards
       Gonzalo

    Hello Michal,
    Yes we need and we are using EOIO, and is not specified in SAP documentation to specify this parameter in the receiver JMS.
    The thing is: Why is missing the mandatory element
    <sap:queueId> for quality of service EOIO?
    I really apreciate any help with this issue.
    Thanks,
    Regards,
    Gonzalo

  • JMS adapter short log

    Hi All,
    Today morning we had a system restart after an upgrade.
    As it is, all the channels were restarted.
    The strange thing is one of the JMS does not have any thing written in the short log in RWB->CC monitoring though the channel is green.
    Can you please let me know what could be the reason for this?
    Regards,
    Raghu

    Hi Raghu,
    There is no specific reason for this kind of behaviour...actually this is unexpected one.
    Once the Java stack have restarted the log will be generated for the channels.
    The reason behind this would be at the time of restart or shutdown any of the instance of this adapter was in use, so even after the Java stack had been restarted the adapter will not be initialized or be supressed.
    I have faced similar kind of thing with even SOAP adapter.
    It depends upon the running instances at the time of shutting down.
    Normally this could happen with SOAP or JMS adapter, if you observe just refreshing or start/stop activity resolve it to norma behaviour.
    I hope this will help you to get some hint.
    Thanks
    Swarup

  • 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!

  • 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

    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

  • JMS adapter could not receive message from Tibco EMS topic

    I'm trying to consume message from tibco EMS topic using Oracle SOA JMS adapter. Can anyone please let me know the steps to do this. Appreciate your help.
    Thanks,
    SB

    Increase Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..

  • Message Conversion in JMS adapter

    Hello Friends,
    I have a scenario where in I will be getting the message from MQ, and the message will look like
    <b>SOURCE</b>
    <Root><MessageHeader><MessageID><MessageIDSystem>SCV</MessageIDSystem><MessageIDType>FE</MessageIDType><MessageIDIdentifier>CUSTOMER_MASTER</MessageIDIdentifier></MessageID><MessageReleaseNo>0004</MessageReleaseNo><MessageVersionNo>00</MessageVersionNo><MessageOrigApplID>SCV</MessageOrigApplID><MessageDestApplID>BROKER</MessageDestApplID><MessageInterfaceID>IDD088</MessageInterfaceID></MessageHeader><MessageBody><SCVData>53435646453030340130303030303401323030372d31312d31362031393a34303a343401313336333938323401330130010154414730303101574542555345525f52454c4154494f4e0155504441544501323030372d31312d31362031393a34303a343301544147303138013836373134013332353030303039343239013332353030303035323338013332353030303035323339010131014e014e01494e41435449564501350154414730303101504552534f4e01494e414354495641544501323030372d31312d31362031393a34303a343401544147303032013332353030303039343239015941553b56414e4553534101333235013301494e41435449564501323030352d30342d30332031383a34363a3136015343563234324d4947524154494f4e01323030372d31312d31362031393a34303a3433014a43473031370133515955493630554b36355136015041015441473031390131013332353030303039343239015041303030303934323901013101544147303033015941550156414e455353410156590101014601013530372d34333032383838013530372d363736383332380149544350545940435750414e414d412e4e4554013201013530372d343330323839310101544147303031014c494e4b01494e414354495641544501323030372d31312d31362031393a34303a3434015441473030360130303432013332353030303035323338013332353030303039343239015343563234324d4947524154494f4e013530372d34333032383838013530372d343330323839310101323030352d30342d30332031383a34363a313601393939392d31322d33312030303a30303a3030015343563234324d4947524154494f4e01494e41435449564501323030372d31312d31362031393a34303a3433014a43473031370149544350545940435750414e414d412e4e4554013530372d343330323839310154414730313901320133323530303030353233380150413b494e5445524558503b48454144510101320154414730313901310133323530303030353233380150413030303035323338010131015441473031390134013332353030303035323338013832373032313030010134015441473031390131013332353030303039343239015041303030303934323901013101</SCVData></MessageBody></Root>
    and the ascii data in this message needs to be converted into XML format.
    JMS Adapter is picking this message from MQ and posting it to XI.
    Also there is an adapter module develped for this conversion and it is working fine for most of the messages, but it failing for this above message.
    Can you please help me out in this issue and how to test that adapter module.
    Thanks & Regards,
    Kumar

    hi kumar,
    >>Can you please help me out in this issue and how to test that adapter module.
    put brek points in ur adapter module and then run ur scenario and debug. this is how u test ur adapter module.
    this will also help u to see why is it running for certain msgs n failin for others. at different steps/points check the value for variables etc while debugging.
    Also put some statements to write audit log entries in ur code for module. this will also help in debugging.
    [reward if helpful]
    regards,
    latika.

  • JMS Adapter: Error executing MQQueueConnectionFactory constructor

    Hello exerts,
    My Sender JMS Comm. Channel is throwing class not found error for com.ibm.mq.jms.MQQueueConnectionFactory. I set my JMS adapter logging level to DEBUG and this is what I got. It is crashing on Constructor. Doesn't anyone have any idea what might be wrong. We have an App server sitting in from on our PI box and they both have same jms libraries on them.
    Thanks, Mayur
    Caught com.sap.aii.adapter.jms.api.base.ConstructorInvocationException: Error executing constructor invocation:
    {ConstructorInvocation
    {className=com.ibm.mq.jms.MQQueueConnectionFactory,
    invokeParams=[]
    }: SAPClassNotFoundException: com.ibm.mq.jms.MQQueueConnectionFactory
    at com.sap.aii.adapter.jms.core.common.InvokeUtils.invoke(InvokeUtils.java:284)

    Hello Experts, just wanted to post an update of this issues. We were able to fix our issues by wipeing out all existing JMS libraries in our PI 7.1 environement and redeploying a fresh library (com.sap.aii.adapter.lib.sda).
    Currently this library contain following JAR files.
    lib/com.ibm.mq.jar
    lib/com.imb.mqjms.jar
    lib/connector.jar
    lib/dhbcore.jar
    lib/com.sap.aii.adapter.lib_api.jar
    Thanks,
    Mayur

  • 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

  • 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.

  • Unable to get BPEL composite with JMS Adapter running.

    Hello All,
    I have tried to build a BPEL Composite to use JMS Adapter, by following the link http://blogs.sun.com/malkit/entry/oracle_soa_suite_bpel_to
    Steps in WebLogic console:
    1. Created a new JMS Server JMSServer-0 (file persistent store) this is targeted to AdminServer
    1. Created a new JMS Module SystemModule-0
    3. Created a connection factory in this module JNDI jms/SendRecvConnectionFactory
    4. Created a queue in this module JNDI jms/ReceiveQueue
    5. Created a SubDeployment Subdeployment0 for these two components.
    6. Created a new JMSAdapter connection pool JNDI eis/tst/TestJMSConn and set the ConnectionFactoryLocation property to jms/SendRecvConnectionFactory
    Next, I created a simple Java client and tested the JMS Queue to work fine. This went well.
    Next, used JDeveloper to create a BPEL Composite to use JMSAdapater, and followed the guidelines given in the above URL to create the JCA file.
    While deploying this BPEL composite, I hit a warning in SOA diagnostic server:
    JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'
    As a result of this warning, the BPEL Composite instances do not get created when I send a message from the test client.
    Please find herewith the log details.
    I am using JDeveloper Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923 and FMW 11g R1 PS3 RC11.
    Any help here?
    [2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.deployment] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] BPEL Component "default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess" successfully loaded.
    [2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.deploy] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] [Deployment] Component: JMSampleProcess was successfully deployed to service engine:implementation.bpel, for composite:JMSSampleProj
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Initializing OutBound_jms.jca
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> OutBound JCAEndpointInteraction::initInteraction - Activating Endpoint Interaction, Endpoint Id='OutBound
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Successfully initialized OutBound_jms.jca
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] EventBus not null
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] component : Component Name: JMSampleProcess[[
    implementation: oracle.fabric.composite.component.implementation.BPELImplementation@51db9e4
    oracle.fabric.composite.model.ComponentTypeModel@51db9e6
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CubeServiceEngine=> initing default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess
    [2011-04-20T08:33:12.458-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Loading InBound_jms.jca ..
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing JCAEndpointActivation::prepareActivation for {PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Locating JCA Binding Component instance: SCA_AS11R1
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:[[
    endpoint='InBound'
    WSDL location='oramds:/deployed-composites/default/JMSSampleProj_rev1.0/InBound.wsdl'
    portType='Consume_Message_ptt'
    operation='Consume_Message'
    activation properties={PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating endpoint (0) for InBound
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Done preparing JCAEndpointActivation for Service 'InBound'
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Successfully loaded InBound_jms.jca
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Initializing InBound_jms.jca
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::performActivation - Performing JCA Endpoint Activation, Endpoint Id='InBound'
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing endpoint activation (1) for InBound
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj Creating new instance of Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - starting Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_start: Jms Adapter started
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_endpointActivation: Activating endpoint Endpoint_1
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_start: Starting endpoint Endpoint_1
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_run: Calling register...
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - successfully completed endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Successfully initialized InBound_jms.jca
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> :defaultRevisionChanged - updated default revision to default/JMSSampleProj!1.0 for default/JMSSampleProj
    [2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21538] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] Removing temporary directory: C:\DOCUME~1\abhatika\LOCALS~1\Temp\1\sar_base_dir_1303306387379.
    [2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21557] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CompositeDeploymentServlet-----> completed deploying sca_JMSSampleProj_rev1.0.jar successfully. Time spent: 5.188 sec.
    [2011-04-20T08:33:13.036-05:00] [soa_server1] [WARNING] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041fd,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'. Resolved 'jms'

    Hi,
    Try targetting it to soa_server1 instead of admin server.

  • Configuration for sync/async bridge in Jms adapter

    Can someone give me a hint what I might be doing wrong?
    The scenario is: synchronous proxy to jms.
    Integration repository:
    Created synchronous outbound interface and synchronous inbound interface, message mapping, interface mapping.
    Integration directory:
    Created jms receiver communication channel and jms sender communication channel and configured them according "How to correlate jms messages".
    Created receiver determination, interface determination and receiver agreement.
    No sender agreement necessary for proxy sender.
    So far so good, but...
    Both the receiver and sender jms adapter have its own queue (the receiving system will get the request in one queue and put the response in another).
    <b>How does the waiting jms receiver adapter know where to expect the answer?</b>
    When I test this scenario the (outbound) message get the status "Log version" (abap moni) and "To be delivered" (java moni).
    PS:
    The testing is performed by using the tool rfhutil. With this tool you can read and write directly from/to the MQ queues where the jms adapters are pointing to.
    After receipt of the request in the queue of the reveicer jms communication channel, I manually put a message in the queue of the sender jms communication channel with the XI message ID filled in the correlation ID.

    More information, In the jms adapter the following error appears:
    XI inbound processing failed for message at time 2007-06-11|11:12:48.908+0100. JMS and XI identifiers for the message are ID:414d512052545849444556312020202045f55b6c20d73102 and 4e5bff20-1804-11dc-c2b4-00096b6ed15c respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Minimum address data not configured. Field InterfaceNamespace is empty.
         at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:1516)
         at com.ibm.mq.jms.MQMessageConsumer.receiveAsyncQ(MQMessageConsumer.java:2538)
         at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4260)

  • Correlation issue in JMS adapter - SYNC/ASYNC scenario without BPM

    Hi,
    I am working on a SYNC/ASYNC scenario with JMS adapter without using BPM. My scenario is SOAP<>PI>JMS. I configured the interface as below:
    1. SOAP Sender channel
    2. JMS Receiver Channel writing to Queue A.
         Module used:      a. RequestOneWayBean
                   b. WaitResponseBean
         Correlation Settings:
                   a. Set JMS Correlation ID to "XI Message ID"
                   b. Store JMS CorrelationID of request (Checked)
                   c. Set JMS Property to "JMS Correlation Id"
                   d. Value = "XI MEssage ID"
    3. JMS Sender channel reading from queue B ( I am exporting the message from queue A and importing into queue B)
         Module used:      a. NotifyResponseBean
         Correlation Settings:
                   a. Set XI MEssage Id to "GUID"
                   b. Set XI Conversation ID to "Stored JMS COrrelationID of Request"
    I can see the cid in the message from queue A. But I observed thhat the header format of the message in Queue A is "MQSTR".
    ISSUE:
    1. While writing the message to queue A, below adapter log details(part b) concerned me:
         a. Message '8747a7c2-2b06-11df-8055-005056a70ed6' successfully processed by channel
         b. Could not create acknowledgements for message '8747a7c2-2b06-11df-8055-005056a70ed6'
    I am not sure why I am receiving the message that "  could not create acknowledgements"
    2. While reading the message from the sender channel,I consistently get the error message as below:
         a. XI message ID corresponding to JMS message with ID 'ID:414d51205341504449442e514d202020c67b954b20005602'
              will be created as a new GUID with value '21bca916-424f-41f6-3347-c71090392b58'
         b. Error while processing message '21bca916-424f-41f6-3347-c71090392b58';  detailed error description:
              com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
              found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
    Below are the blogs which I have already gone through:
    1. JMS Synchronous Scenario without BPM - Correlation Settings and Transactional JMS Session
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
    2. Note: 1086303
    3. Sync / Async Bridge without BPM
    In the note, they mentioned something about header being "MQRFH2". BUt in our case, the header is "MSSTR". Not sure whether it makes any difference.
    Please help.
    Edited by: GP on Mar 9, 2010 4:24 AM

    Hi,
    detailed error description:
    com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
    found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
    This error would generally arose when there are multiple messages, got stuck in the outbound queue. Try to stop both the sender and receiver JMS comunication channels and clear both the inbound and outbound queues.
    Once all the messages in the queue are cleraed, try posting the message again.
    Regards,
    Swetha.

Maybe you are looking for