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

Similar Messages

  • File to JMS Scenario - Error is Receiver JMS Adapter

    Hi,
    I am working on File to JMS scenario. I have deployed all required jars for MQ 6.0.2 in SDM. Create all MQ related objects. I am getting following error for Receiver JMS adapter in CC Monitoring.
    Please let me know if I have missed anything. Is there anything to do in Visiual Administrator->JMS Provider or JMS Connector for these kind of Scenarios?
    Thanks in Advance...
    Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
    at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
    at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
    at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
    com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
    MQJE016: MQ queue manager closed channel immediately during connect
    Closure reason = 2009
    at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

    Hi,
    I have made my Qmanager as default Qmgr. Now the error is :- Socket connection attempt refused
    Recv JMS Communication Channel Error:-
    Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
    at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
    at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
    at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
    com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
    MQJE011: Socket connection attempt refused
    at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

  • Error in Inbound JMS adapter(in ESB project)

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

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

  • Error in Inbound JMS adapter (ESB project)

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

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

  • Error in reciever JMS adapter  (SENARIO  FILE - XI- JMS )

    HI everyone,
    My previous error is solved (Error in getting initialcontext). I have deployed the required jar files on server.
    Thanks to you'll.
    Now I am getting the following error in JMS adapter monitoring RECIEVER CHANNEL . NO DETAIL INFORMTION SET.
    i AM USING IBM websphere MQ series for recieving JMS messages from XI.
    I have made Queue manager,
    Queue,
    reciever channel.
    and have also provided the following details in my communication channel in XI
    QueueConnection FactoryJavaClass : com.ibm.mq.jms.MQQueueConnectionFactory
    QueueJavaClass : com.ibm.mq.jms.MQQueue
    Ip address or server name : <my ip address> since i have installed IBM JMS server on my system.
    server port :1415
    QueueManagerName :QM_apple
    channel name : reciever_channel
    jms Queue: Q1
    character set id (ccsid): This I have not given , Idont know what to give here
    Transport protocol :tcp/ip
    Please guide me to go further , I am stucked at the error , No reciever details set. What should i do?

    Hi  Deepak ,
    Please refer this forum post .. if this helps.
    Reg:Receiver Mail Adapter
    Regards,
    srinivas

  • Error status in JMS adapter - sync / async brigde. Message processed ok

    Hi guys
    I'm having som trouble with my scenarion. I'm sending sync message from SAP backend to XI using proxy. From XI onwards to JMS adapter async (and the other way around for the response message).
    This works OK. However i have a status error in my RWB on the JMS adapter. There is er red exclamation mark and a text saying:
    Correlation ID 'XXX' of JMS request message 'ID:yyy' saved that correponds to XI message 'XXX'
    How do I get my adapters in status green?
    Kind regards
    Martin

    Hi Kai
    Oh - OK
    Settings are:
    Receiver JMS channel:
    Set JMSCorrelation to: XI Message ID (MessageID)
    Store JMS CorrelationId of request: Mark
    Sender JMS channel:
    Set XI Message ID (MessageID) to: GUID (Recommended Value)
    Set XI Conversation ID (ConversationID) To: Stored JMS CorrelationId of Request.
    Kind regards
    Martin

  • Error initializing Sender JMS Adapter

    Hi,
      Has anyone integrated MQSeries 5.3 with XI 3.0? I have placed all the necessary jar files under tech_adapter and in class path.My adapter status is red and the log says that
        ". ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
                at java.lang.Class.getConstructor0(Native Method)
                at java.lang.Class.getConstructor(Unknown Source)
                at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
                at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
                at java.lang.Thread.run(Unknown Source)"
    please let me know if i am missing something.
    Regards
    Sathya

    Hi Amol,
           Our SLD Accessor service is working properly.i have deployed all the necessary jar files.I am not very confident in my class path settings.So i am sending my class path,
           D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\classes12.zip;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqjms.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mq.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\connector.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqbind.jar;D:\usr\sap\BWXI\SYS\global\tech_adapter\server.jar;com.sap.aii.messaging.adapter.AdapterImpl;D:\usr\sap\BWXI\SYS\global\tech_adapter\ejb.jar;
    please look into that.
    I am sending the log trace for Adapter Configuration so that you can make something out of it.
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Starting adapter engine version 3.0.0318 ($Id: //tc/aii/30_REL/src/_messaging/java/com/sap/aii/messaging/adapter/AdapterImpl.java#7 $, $DateTime: 2004/08/03 11:19:35 $ ) ...
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: sync.time: 200411110440
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jdk.version: 1.3.1
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.rel: 30_REL
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: build.date: 2004-11-11 04:58
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: latest.change: 300224
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.server: PWDFM060
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter_base.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: initializing and starting with given Parameters ...
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:  - Token File token.keystoragenot found
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Reading property file 'adapter_base.properties' for adapter modules configuration...
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: adapterID set to Adapter1
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   AdapterMonitor      - expects property file  'BaseConfiguration/AdapterMonitor.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module AdapterMonitor
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module AdapterMonitor
    Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-0,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleAdapterMonitor' created, version 2.0.1010
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module AdapterMonitor
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module AdapterMonitor
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   InfoLogger      - expects property file  'BaseConfiguration/InfoLogger.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module InfoLogger
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module InfoLogger
    Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-1,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleInfoLogger' created, version 2.0.0918
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module InfoLogger
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module InfoLogger
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   IDLogger      - expects property file  'BaseConfiguration/IDLogger.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module IDLogger
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module IDLogger
    Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-2,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleIDLogger' created, version 1.0.0523
    Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: Initializing new IDLogger object(version 1.0.0523), root directory is 'Data'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module IDLogger
    Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: IDLogger started
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module IDLogger
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   RtcMonitor      - expects property file  'BaseConfiguration/RtcMonitor.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module RtcMonitor
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module RtcMonitor
    Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-3,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleRtcMonitor' created, version 1.0.0819
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module RtcMonitor
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module RtcMonitor
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   PersistLayer      - expects property file  'BaseConfiguration/PersistLayer.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PersistLayer
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module PersistLayer
    Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-4,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePersistLayer' created, version 2.0.0929
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module PersistLayer
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module PersistLayer
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   PWtokens      - expects property file  'BaseConfiguration/PWtokens.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PWtokens
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module PWtokens
    Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-5,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePWtokens' created, version 1.0.0724
    Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Initializing new PWtoken object(version 1.0.0724), root directory is '.'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module PWtokens
    Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '<!%' set for parameter 'PWD.beginSeparator'
    Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '%!>' set for parameter 'PWD.endSeparator'
    Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: SLDaccessor started
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module PWtokens
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   GUIBrowserEngine      - expects property file  'BaseConfiguration/GUIBrowserEngine.properties'
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module GUIBrowserEngine
    Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module GUIBrowserEngine
    Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-6,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleGUIBrowserEngine' created, version 3.0.1930
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module GUIBrowserEngine
    Apr 26, 2006 10:08:23... ...saging.adapter.ModuleGUIBrowserEngine [Thread[Thread-6,5,main]] Info: GUIBrowserEngine started
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module GUIBrowserEngine
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   HttpServer      - expects property file  'BaseConfiguration/HttpServer.properties'
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module HttpServer
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module HttpServer
    Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-7,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleHttpServer' created, version 1.0.0808
    Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Initializing new HttpServer object(version 1.0.0808), root directory is '.\Data'
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module HttpServer
    Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Http server started
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module HttpServer
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   SLDaccessor      - expects property file  'BaseConfiguration/SLDaccessor.properties'
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module SLDaccessor
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module SLDaccessor
    Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-9,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleSLDaccessor' created, version 2.0.1010
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module SLDaccessor
    Apr 26, 2006 10:08:23... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: Initializing new SLDaccessor object(version 2.0.1010), root directory is '.\Data'
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module SLDaccessor
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   jms_sender2is      - no property file specified  - try default 'Configuration/jms_sender2is.properties
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   jms_sender2is      - expects property file  'Configuration/jms_sender2is.properties'
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module jms_sender2is
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module jms_sender2is
    Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-11,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleJMS2Transport' created, version 2.0.1626
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module jms_sender2is
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine startup procedure finished: 9 modules started successfully
    Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine running...
    Apr 26, 2006 10:08:23...  com.sap.aii.messaging.adapter.IDLogImpl [Thread[Thread-11,5,main]] Info: Attached persistent hashtable to file 'D:\usr\sap\BWXI\SYS\global\tech_adapter\Data\jms_sender2is_ID.dat'
    Apr 26, 2006 10:08:23... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-11,5,main]] Info: Created new ID log file 'jms_sender2is_ID.dat' in folder 'Data' for module 'jms_sender2is'
    Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.SenderParty'
    Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.ReceiverParty'
    Apr 26, 2006 10:08:23... ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
         at java.lang.Class.getConstructor0(Native Method)
         at java.lang.Class.getConstructor(Unknown Source)
         at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
         at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
         at java.lang.Thread.run(Unknown Source)
    Apr 26, 2006 10:08:28... ...duleSLDaccess.createAdapterEntities() [Thread[Thread-9,5,main]] Info: Adapter Entities for AdapterEngine_bwxi_8200 created successfully
    Apr 26, 2006 10:08:29... ...duleSLDaccess.createAdapterServices() [Thread[Thread-9,5,main]] Info: Adapter Services for AdapterEngine_bwxi_8200 created successfully
    Apr 26, 2006 10:08:29... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: SLDaccessor started
    Regards
    Sathya

  • Error in Receiver JMS Adapter

    Hi,
    We are having a problem in production, there is an interface which runs ok most of the time but sometimes it's throwing exception
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Unable to write new JMS message body for message: 4b4abe9e-24ff-007d-e100-80000a02210b: ConnectorException: Connector for ConnectionProfile of channel: Srv_WMS_VIC_JMSReceiveron node: 6532450 having object id: 966e2f3c527c359fbe4e1a1f902bf7d0 was unable to create a new javax.jms.TextMessage message: java.lang.NullPointerException
    Then alert raises and someone has to manually stop and start the channel and resend the message in error.
    This has been really annoying the support people and getting serious impact on business.
    Does anyone has an idea why it is happening and what can be the resolution for the same.
    Regards
    Ria

    Ria,
    Is the exception  throws after the  restart of the  Queue/ Receiver Server ?
    Check - Note 856346
    Cheers
    Agasthuri

  • Reveiver JMS Adapter error

    Hi All,
    we are getting the folowing error in Receiver JMS adapter.
    Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: The JMS channel with channel ID 88259a4ea44537c6b7f6c08de5630e2a is errornous. Details:Problem with JMS queue connection; provider error code: C4002, provider error message: [C4002]: Read packet failed. - cause: java.net.SocketException: Connection reset: com.sap.aii.af.service.jms.XIJMSException: The JMS channel with channel ID 88259a4ea44537c6b7f6c08de5630e2a is errornous. Details:Problem with JMS queue connection; provider error code: C4002, provider error message: [C4002]: Read packet failed. - cause: java.net.SocketException: Connection reset
    I look forward to hearing from you.
    Thanks,
    Jag

    Hi,
    Please see if the JMS channel is open and have mentioned properly.
    along with it look if the Queue manager is fine.
    Threads that have the same issues:
    connection with the JMS provider
    configuration of JMS  adapter Using WebSphereMQ
    Thanks
    Swarup

  • Error in JMS adapter 11g

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

    Have you tried cross-domain security or domain trust?

  • JMS adapter does not recover from error

    Hello everyone,
    We are noticing some strange behavior with the JMS adapter, and would like your help. We have messages coming into XI from WebSphere MQ. We have configured a Sender Comm channel (MQ_SENDER) with the appropriate JMS adapter, with a specified queue name (TEST.Q) . We have installed the appropriate MQ-JMS libraries for v6.0.
    Here's the problem scenario... initially the application sending the messages to the specified queue was putting an incorrectly formatted MQRFH2 structure in the message. Predictably, this caused our comm channel to fail, and it shows up on the adapter monitor in the failed state with the message "MQJMS1050: The MQRFH2 header has an incorrect format Code: MQJMS1050". This in itself is not a problem, we realized that the application was sending a malformed message. The problem occurs when we fixed the sending application to completely strip out the MQRFH2 header altogether. When the new message is sent, the comm channel seems "stuck" on the previous error, and does not even pick up the new message from the queue. The adapter monitor continues to show the same error for the comm channel. Now when we modified the comm channel to read from a DIFFERENT queue (TEST2.Q) , the comm channel got out of the error state and is able to successfully process new messages coming into that queue. However, when we revert the comm channel back to the original queue (TEST.Q) it reverts back to the original MQJMS1050 error, and does not pick up new messages on the queue.
    Any assistance would be greatly appreciated...

    Hi,
    1) Try to refresh the metadata
    2) Check the Queue status
    3) Once again check the Queue name. try to make the Sender JMS adapter inactive .save  it..again make it active  and  save it and  activate the object.
    4) Refresh the Cache :
    a)Start transaction SXI_CACHE.
    b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
    If you still face issue try this .
    Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
    However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
    To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
    Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
    Regards
    Agasthuri Doss

  • Sender JMS Adapter error: The JMS provider gave the error message as Not permitted, and the error code is null

    I am trying to connect tibcoems with PI using a Sender jms adapter.After successfully installing the drivers , the sender adapter goes into error.
    "The JMS Provider gave the error message as Not permitted, and the error code is null"
    The Transport protocol is 'Access JMS Provider with JNDI' and i have been given the required parameters from the tibco guys.
    Your input are highly appreciated.
    Shyam

    Hi AQmit,
    Thanks for the reply.
    Please find the screenshots of what i am trying to do.
    Also, Can u direct me how to check the right logs?

  • 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

  • JMS Adapter Error: RecoverableException

    Hi all!
    Sometimes our JMS Receiver Communication Channels fail without any reason... The errors in the audit log of the messages are:
    Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException
    Error Exception caught by adapter framework: null
    Error Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException.
    We have to manually restart the channels in the Communication Channel Monitoring application and after to resend the messages... In my opinion it is not admissible in a production environment.
    ¿Do you have any idea about these errors?
    Thanks in advance!
    Best Regards,
    Roberto
    SAP PI Technical Consultant

    Hi,
    The transport protocol is: Access JMS Provider with JNDI
    The JMS Provider is an Oracle OC4J server. This provider is used to connect with the Oracle AQ queues.
    Best regards,
    Roberto

  • 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

Maybe you are looking for