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.

Similar Messages

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

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

  • Inbound JMS adapter with MapMessage

    I'm sharing the following problem and solution with using the OEP inbound message adapter because it may be
    a common situation occurring to other users.
    Recently was using the inbound JMS adapter with its default (OEP internal) converter from JMS MapMessage
    messages to OEP events. The inbound adapter was receiving MapMessage messages but it was not assigning
    values to the corresponding attributes in the specified input event instance.
    The problem was that I was not properly creating the MapMessage messages in the JMS producer client.
    I was using method setStringProperty() instead of method setString(), which is what is needed to set name/value
    pairs of type String, and similarly with other primitive Java data types. Here's a code snippet for building and sending
    a MapMessage on the client side:
          try {
          mapm = qsess.createMapMessage();
          mapm.setString("valueType1", "value1");
          mapm.setString("valueType2", "value2");
          mapm.setInt("valueType3", 5);
          producer.send(mapm);
         } catch (JMSException jmse) {
         jmse.printStackTrace(System.err);
         System.exit(0);
    Regards,
    Mauricio

    OSB JMS config:
    <queue name="RequestQ">
    <sub-deployment-name>wlsbJMSServer</sub-deployment-name>
    <jndi-name>RequestQ</jndi-name>
    </queue>
    <queue name="ResponseQ">
    <sub-deployment-name>wlsbJMSServer</sub-deployment-name>
    <jndi-name>ResponseQ</jndi-name>
    </queue>
    Business service in OSB from where message is sent to the "ResponseQ" which is consumed by CEP.
    Jms Inbound CEP Config:
    <jms-adapter>
    <name>jmsAdapterInbound</name>
    <jndi-provider-url>t3://10.227.145.164:7005</jndi-provider-url>
    <connection-jndi-name>weblogic.jms.XAConnectionFactory</connection-jndi-name>          
    <destination-jndi-name>ResponseQ</destination-jndi-name>
    <user>weblogic</user>
    <password>weblogic123</password>
    <work-manager>JettyWorkManager</work-manager>
    <concurrent-consumers>1</concurrent-consumers>
    <session-transacted>false</session-transacted>
    </jms-adapter>

  • CEP with inbound JMS Adapter

    Problem: The inbound adapter is not triggered at all.
    I have an EPN with an inbound JMS adapter listening to a JMS Queue hosted in my 11g Jdev SOA Suite. The queue is populated from a SOA composite. I can see the messages in the queue and my CEP application is deployed succesfully, but my JMS Adapter doesn't get any.
    Here's the relevant section from EPN xml file:
    {color:#3366ff}&lt;bean id="OrderConverter" class="agb.foc.order.OrderMessageConverter"/&gt;
    &lt;wlevs:adapter id="OrderIn" provider="jms-inbound"&gt;
    &lt;wlevs:instance-property name="converterBean" ref="OrderConverter"/&gt;
    &lt;/wlevs:adapter&gt;
    {color}
    Here's my jms-adapter xml file:
    {color:#3366ff}&lt;jms-adapter&gt;
    &lt;name&gt;OrderIn&lt;/name&gt;
    &lt;jndi-provider-url&gt;t3://localhost:7001&lt;/jndi-provider-url&gt;
    &lt;connection-jndi-name&gt;weblogic/jms/ConnectionFactory&lt;/connection-jndi-name&gt;
    &lt;destination-jndi-name&gt;agb/jms/TestQueue&lt;/destination-jndi-name&gt;
    &lt;user&gt;weblogic&lt;/user&gt;
    &lt;password&gt;weblogic&lt;/password&gt;
    &lt;concurrent-consumers&gt;1&lt;/concurrent-consumers&gt;
    &lt;session-transacted&gt;false&lt;/session-transacted&gt;
    &lt;/jms-adapter&gt;{color}
    And the queue details from the weblogic admin console:
    {color:#3366ff}Name: AgbTestQueue
    Type: Queue
    JNDI Name: agb/jms/TestQueue{color}
    Note: I'm using CEP 10gR3 with Eclipse IDE and 11g Jdeveloper SOA suite internal release which comes after TP4.
    Thanks in advance
    Alosh
    Edited by: aloshbennett on Feb 9, 2009 10:44 PM
    formatting

    UPDATE:
    If I send the messages via a standalone java client, CEP is accepting them.
    The difference I see in both the messages is
    {color:#c0c0c0}SOA messages arrive in the queue with JMSXDeliveryCount property set to 1, while standalone client messages arrive in the queue with JMSXDeliveryCount set to 0.
    {color}
    {color:#c0c0c0}
    Why does the messages from SOA composite arrive with JMSXDeliveryCount set to 1? Why does that prevent CEP from receiving them?{color}
    EDIT Again: The messages look identical from the admin console. The JMSXDeliveryCount goes up because the delivery to CEP fails and it could be a red herring.
    If I export the messages from SOA Composite to a file and import them back, CEP picks them up.
    Help!
    Edited by: aloshbennett on Feb 10, 2009 8:09 AM

  • 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 in Inbound File Adapter

    Hello,
    The scenario :
    Flat File => XI => Enterprise (4.7)
    I'm getting the following error in the Adapter Engine at time of Reloading the new inbound file adapter.
    ==========
    <i>***** Tue Jul 06 11:46:54 EDT 2004 *****
    11:46:59 (4023): File adapter initialized successfully
    11:46:59 (4007): File adapter started
    11:47:03 (4050): ERROR: Unexpected exception "com.sap.aii.messaging.adapter.ftp.FTPEx: Unknown extension in database file name." occurred</i>
    ==========
    The inbound file adapter is as below ... :
    ==========
    <i>classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
    mode=FILE2XMB
    XMB.TargetURL=http://host123:8001/sap/xi/engine?type=entry
    XMB.SenderBusinessSystem=Sender_System
    XMB.SenderInterfaceNamespace=http://abc.com/xi/
    XMB.SenderInterfaceName=DataFile_Out
    XMB.User=xisuper
    XMB.Password=xipass
    XMB.ReceiverBusinessSystem=ENT
    XMB.ContentType=text/plain
    XMB.ContentKind=T
    XMB.QualityOfService=EO
    file.sourceDir=
    file.sourceFilename=DATAFILE
    file.processingMode=test
    file.pollInterval=060
    ftp.host=100.200.300.400
    ftp.port=21
    ftp.user=userid
    ftp.password=passwd
    ftp.mode=Text</i>
    ==========
    Any help is greatly appreciated.
    Thanx in advance.
    Homiar.

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

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

  • Setting JMS Message header and properties in JMS Adapter ESB Component

    Hi,
    I am new to using some of these adapters in Oracle ESB and need some help.
    I am trying to define a JMS Publisher using JMS Adapter component in JDeveloper. I would like to publish messages with message property set to a topic. I dont find a way to do that.
    I see that for consuming JMS messages, the JMS Adapter allows to specify message selector but I could not find a way for producing message with a user defined message property. I would like to use that property in the message selector to filter messages and consume.
    I am using Oracle SOA Suite 10.1.3.3.x
    Can someone help please?
    Thanks.

    Thanks for the response.
    I think I found the solution although I havent tried it out yet.
    ESB sample 110.JMStoJMSHeaders outlines the approach.
    It is my understanding that JMS Message selector can work on JMS header or JMS properties (user defined) but not on JMS body. (All the three constitue a JMS message). Hence the need to set a JMS property prior to publishing the message to a topic/queue.
    Thanks.

  • 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

  • JMS Adapter UseMessageListener property...

    What is the use of the 'UseMessageListener' property that needs to be set as true / false while configuring an Inbound JMS Adapter Service. What difference does the true / false value make to the runtime working of the Service? Thanks in advance.

    Hi,
    This is supposed to solve ERRJMS_PROVIDER_ERR error for JMS adapter.
    Please refer metalink NOTE:393468.1.
    I am not sure if it works for 10.1.2.0.2 version but probably it works on 10.1..3.X version.
    Regards,
    Ved

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

Maybe you are looking for

  • 2.4G Mixed Mode vs N Only

    I have a AE6900 router, and most of my home devices are supporting N mode, but one media device is B/G mode supported only. When I set my router to N only, most of my devices are working very well, get the maximum connection speed, however it turns d

  • 7.6 upgrade Ipod no longer recognised

    I upgraded itunes to 7.6 this morning and now my Ipod is no longer recognised when I connect it. I have plugged it into another pc with an earlier version of itunes and have no problems. Anyone else having this problem? Is there a way to fix it - wit

  • Crystal Reports 11g Performance Issue

    We just upgraded our database to Oracle 11g from Oracle 10g and we are having significant performance issues with Crystal Reports. Our DEV and TEST environments are on 11g and are very slow to connect to the database and attach to specific tables.  I

  • BAPI to create Steel Surch Debit (From VA01 Transaction)

    Hi, I need a bapi to create steel surch debit,if we give order type zdr1 in va01 it will create a steel surch debit memo,I tried with BAPI 1.BAPI_SALESDOCU_CREATEFROMDATA1 2.BAPI_SALESDOCU_CREATEFROMDATA2 3.BAPI_SALESDOCU_CREATEFROMDATA 1st  and 2nd 

  • Emails Disappears from Device

    Hi, Emails on my 8320 disappears from my device frequently without me deleting it on Outlook or on my device. Sometimes it happens every few days while other times, it happens in a week or two.   While the emails still remain in Outlook, I would wish