Configuration of JMS receiver  Using Jboss JMS provider

Hi all..
I am configuring JMS adapter as receiver.
I am using JMS provider JBOSS .
I hav done configuration as
Transport protocol :Acess JMS provider with JNDI
JNDI lookUp Name of q connection factory: org.jboss.naming.LinkRefPairService
Name of JNDI initial Context factory :org.jnp.interfaces.NamingContextFactory
in sxmb_moni I am getting blak&white flag
IN Run time work bench In adapter monitoring I am getting
Receiver channel. Details: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory.
Can anybody plz tell me why this haapend?

Did you deploy the JMS client jars to the J2EE Engine?
Cannot instantiate class: org.jnp.interfaces.NamingContextFactory  sounds like the Framework can't find the class.
Take a look here:
Re: Using JBOSS JMS provider with XI
Greetz
      Sebastian
Message was edited by: Sebastian Simon

Similar Messages

  • Using JBOSS JMS provider with XI

    Hi,
    I am connecting XI to a custom Java application developed on JBOSS app server.  The custom application is developed with connectivity using JMS.  I was told that JBOSS has a JMS provider used by the custom app.  Has anyone done this before?  Is it possible for XI to use JBOSS JMS provider?  How difficult is this going to be for synchronous interface?  Any information is greatly appreciated.
    thanks.
    James Chang

    hi,
    first deploy jboss-j2ee.jar,jms.jar,dom4j-full.jar..for deploying these jars into the xi follow this link
    http://help.sap.com/saphelp_nw04s/helpdata/en/33/e6fb40f17af66fe10000000a1550b0/frameset.htm
    then to make use of the JMS adapter follow this link,
    http://help.sap.com/saphelp_nw04s/helpdata/en/4d/a3bc97ff55c742af7faed661635baf/frameset.htm
    hope this will be useful.....
    regards,
    Sundararamaprasad

  • Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper

    Hello
    Has anyone managed to set the DCJMSCorreleationID dynamic attribute in a JMS RECEIVER using Seeburger AttribMapper module?
    Here is how I configured the JMS_RECEIVER:
    In the module tab, I added a new module:
    Module Name     Module Type     Module Key
    localejbs/Seeburger/AttribMapper     Local Enterprise Bean     map
    And I added the following parameter:
    Module Key     Parameter Name                                                       Parameter Value
    map                     http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID  "TEST"
    When I process a message, I can see in the adapter engine Audit log the following lines:
    SEEBURGER/AttribMapper: Setting dynamic property http://sap.com/xi/XI/System/JMS - DCJMSCorreleationID = TEST
    SEEBURGER/AttribMapper: Finished succesfully, 1 properties set or deleted     
    However looking at the Message Content/SOAP Document, I can see no dynamicConfiguration (it should be the case according to Seeburger documentation).
    If I check the message properties on the JMS queue, I can see the correlation ID is not set to TEST.
    Any idea?
    Thanks in advance!
    Greg

    Are you using the AttribMapper in the Sender or in the Receiver Channel ? Please be aware that you will not be able to see the change of attribmapper in the message content in receiver channels (they are not updated/persisted there).

  • Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper

    Hello,
    I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
    In the module tab, I added a new module:
    Module Name Module Type Module Key
    localejbs/Seeburger/AttribMapper Local Enterprise Bean map
    And I added the following parameter:
    Module Key Parameter Name Parameter Value
    map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
    When processing a message, I get the following error on the Communication Channel Monitoring:
    Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
    Does anyone has an idea on how to fix this problem?
    Thanks for your help!
    Benoit

    HI,
    Refer the discussion of
    Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
    Dynamic subject in AS2 receiver
    Thanks
    Swarup

  • Using Weblogic JMS for internal delivery channel

    hi,
    I want my B2B to talk to back-end application through Weblogic JMS queues. I have configured internal delivery channel for this. I am getting error message 'Max retry exceeded' in b2b_idc_transport.log
    2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
    2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) JMSReceiver.init() started ....
    2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) Establishing JMS Connection.
    2008.09.24 at 12:10:03:704: B2BStarter thread: (DEBUG) Establishing JMS Connection.
    2008.09.24 at 12:15:03:428: B2BStarter thread: (ERROR) Max retry exceeded, closing everything
    java.lang.Exception: Max retry exceeded
         at oracle.tip.transport.basic.jms.JMSMonitor.reconnect(JMSMonitor.java:833)
         at oracle.tip.transport.basic.JMSReceiver.init(JMSReceiver.java:333)
         at oracle.tip.transport.b2b.B2BTransport.init(B2BTransport.java:379)
         at oracle.tip.adapter.b2b.transport.AppTransportInterface.initialize(AppTransportInterface.java:282)
         at oracle.tip.adapter.b2b.engine.Engine.initialize(Engine.java:512)
         at oracle.tip.adapter.b2b.init.B2BServer.initialize(B2BServer.java:280)
         at oracle.tip.adapter.b2b.init.B2BStarter.startB2B(B2BStarter.java:297)
         at oracle.tip.adapter.b2b.init.B2BStarter.run(B2BStarter.java:143)
         at java.lang.Thread.run(Thread.java:534)
    I have applied latest patch 7322333.
    kindly let me know what is workaround for this? also, how can do debugging of this issue in B2B.
    Thanks in advance.
    Regards,
    Vaibhav
    Edited by: vaibs on Sep 26, 2008 12:15 AM

    hi Sinkar,
    Thanks for reply. I have checked connectivity from b2b server to weblogic server, using java stub. Stub can connect to the Q successfully.
    here is my b2b.log
    2008.09.24 at 12:09:49:233: main: B2B - (DEBUG) B2B initialize
    2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) This is Main thread executing..
    2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start
    2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start - context started
    2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG) B2BStarter - This is B2BStarter thread executing..
    2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG)
    Maximum Heap Size = 530907136
    Memory Allocated = 8323072
    Free Memory = 842560
    2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) ExecutionContextManager initialization is done
    2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) User's maxCachedSessions is set to 0
    2008.09.24 at 12:09:50:560: B2BStarter thread: B2B - (DEBUG) B2BStarter - Context Initialized
    2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Start B2B
    2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Starting B2B
    2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - configuration oained
    2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - clear global cache
    2008.09.24 at 12:09:51:793: B2BStarter thread: B2B - (DEBUG) XEngine not running. So no need to clear cached objects inside XEngine.
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [0] HL7 over MLLP Exchange
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [1] EDI X12 over AS1
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [2] Custom Document over Generic Exchange
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [3] EDI EDIFACT over Generic Exchange
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [4] RosettaNet over RNIF
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [5] EDI X12 over Generic Exchange
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [6] Custom Document over MLLP Exchange
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [7] Custom Document over AS1
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [8] EDI EDIFACT over AS1
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [9] HL7 over Generic Exchange
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (NIFORMATION) Repository:print: [10] Custom Document over Internet
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [11] Custom Document over ebMS
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [12] EDI X12 over Internet
    2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [13] EDI EDIFACT over Internet
    2008.09.24 at 12:09:51:981: B2BStarter thread: B2B - (DEBUG) Repository:constructCertSQL SELECT cert.ID, cert.CLASSTYPE FROM TIP_Certificate_ra cert, TIP_Party_ra party, TIP_DocumentExchange_ra docex WHERE cert.ID = docex.signingcredential AND cert.tradingpartner = party.ID AND party.ishosted != 'Y'
    2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Enter
    2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Envelope
    2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Message Header
    2008.09.24 at 12:09:52:386: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Exit
    2008.09.24 at 12:09:52:402: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Enter
    2008.09.24 at 12:09:52:433: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Exit
    2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Enter
    2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize resetListener = true
    2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initdcx = true
    2008.09.24 at 12:09:52:543: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize TPAProcessor
    2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Clear TPA Cache
    2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize DataContext. Pool Size 0
    2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Treat Response as Request = false
    2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Exit
    2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize Transport
    2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Initialize Transport Logger.
    2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Transport LogLevel = STATUS
    2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) Repository:getDeliveryEndPointList: Putting http://localhost
    2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) oracle.tip.adapter.b2b.transport.TransportInterface:initialize: Props: http://localhost port = 7777
    PROTOCOL_ENDPOINT = null
    2008.09.24 at 12:09:52:636: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [Wholesale_Transport_Server < http > < Wholesale >]
    2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize Initialize AppTransport Logger.
    2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize AppTransport LogLevel = WARNING
    2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (INFORMATION) Repository:getInternalDeliveryEndPointList: Putting jms://[email protected]
    2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize main Endpoint loop jms://[email protected]
    2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize looping through transport Endpoint: jms://[email protected]
    2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize add jms transport Endpoint: jms://[email protected] {Destination Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.destination_password=weblogic, Connection Factory Location=weblogic.jws.jms.QueueConnectionFactory, jms.receiver.jndi_connection_factory_location=weblogic.jws.jms.QueueConnectionFactory, isTopic=false, Message Type=bytes, jms.receiver.is_topic=false, jms.receiver.factory_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, transport_callout_waittime=30, jms.receiver.jndi_destination_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.polling_interval=10, polling_interval=10, Factory Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.jndi_destination_location=[email protected], jms.receiver.destination_username=weblogic}
    2008.09.24 at 12:09:53:713: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
    2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
    2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
    2008.09.24 at 12:35:52:276: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
    2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
    2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
    2008.09.24 at 12:35:52:884: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize Enter
    2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize B2BListen turned off, will not listen on IP_OUT_QUEUE for messages
    2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run start listening on message
    Thanks,
    Vaibhav
    Edited by: vaibs on Sep 28, 2008 3:20 AM

  • JMS receiver adapter configuration error

    Hi All,
    I am facing an issue with JMS receiver adapter. My Configuration parameters for receiver adapter are as follows.
    1.Transport protocol:WebspherMQ (MQSeries) JMS provied
    2.Message porotocol:JMS 1.x
    3.Adapter Enigen: Integration Server
    4.QueueConnecation Factory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
    5.Queue Java Class:com.ibm.mq.jms.MQQueue
    6.IP Address or server name:<Host Name>
    7.Server port:1414
    8.Queue Mannager Name:TestQM
    9.channal name:Recv_Channel
    10.JMS queue:SAP_PI
    11.Transport/netwrok protocol:TCP/IP
    12.JMS compliant:WebSpherMQ(non jms)
    13.Delivery mode of message Producer:Persist JMS Messages in the JMS provider
    14.Mapping of message:Message Payload=JMS Payload
    In adapter monitor, the adapter status shows below error.
    <b>Receiver channel. Details: (No detail information set.)</b>
    I have already installed the external drivers for JMS adapter. Can someone help me if I am missing some parameter in the above configuration.
    Thanks in advance
    Regards,
    Ashish

    Hi,
    I am getting the below error in Audit Log.
    Error - Exception caught by adapter framework: The JMSSender returned no JMSTextMessage to use. Must abort send process.
    Error - Delivery of the message to the application using connection AFW failed, due to: The JMSSender returned no JMSTextMessage to use. Must abort send process..
    Can someone please help me in resolving this issue...
    Thanks in advance.
    Regards,
    Ashish

  • How create JMS using jboss server

    Hi
    I am new to JMS, as i need to know how to create a JMS client in JBoss, i need complete details about jms topic/queue, complete details including the configuration in jboss to create a sample jms client.
    Thanks in advance.
    regards
    Javith

    Hi Javith
    The top three links provided in a Google search 'jboss jms tutorial' look like they'd cover this pretty well -- depending on if you're using JMS inside the JavaEE environment, or your using JMS directly. We might be able to help you more if you were trying to use GlassFish Message Queue and/or GlassFish Enterprise Server.
    Good Luck
    -- Ed

  • Error while using webmethod JMS provider with JNDI

    Hi,
    I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc. 
    While activated the adapter short log shows: Adapter has not provided any status information about this channel"
    In the detailed log following error message is displayed: "Obtained connection factory: null#"
    #1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
    #1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
    #1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
    #1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
    #1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
    at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
    at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
    at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
    at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
    at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
    at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
    at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    #1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
    #1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
    Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.

    Hi,
    Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
    Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
    Regards,
    Srini

  • JMS Receiver Adapter, using JMS Properties

    Hello,
    with XI SP14 i should be able to set JMS Properties using Adapter Specific Message Attributes DCJMSStringProperty1 and DCJMSStringProperty2. I set the Elements DCJMSStringProperty(1,2) during java mapping and everything works fine. i can see the "DynamicConfiguration" in the Message monitoring appearing with the correct values.
    In the configuration of the adapter specific attributes i give the message properties names and hope the adapter will pass the the values to the jms (IBM MQ implementation) but in jms no properties appear.
    has anybody a hint for me, has anybody faces similar issues.
    best regards,
    roland

    Hi Prasad
    You can use a simple user defined function. The question is, to which destination element should the function be connected to? I tried to connect to the root element of the destination structure (as dummy) and it worked.
    I prefer JAVA Mapping it's more transparent and reusable.
    Btw. My original problem remains still unsolved. Our IBM MQ still cannt see the JMS Properties.I contacted SAP for this matter, I will provide you with the solution when there is any.
    Greetings
    Roland
    Message was edited by: Roland Stellmach

  • JMS Receiver Adapter configuration help

    Hi Experts,
    In our scenario, we need to integrate MQ series with SAP PI, where in we are using JMS Sender and Receiver adapters to put and get the mssg from correponding IBM MQ queues.
    Using Sender JMS Adapter we are consuming a txt mssg by specifying corresponding module configuration parameters, which is for converting into a XML mssg.
    The issue is with JMS Receiver adapter, Inorder to get an XML mssg apart from standard/default entries ... do we need to maintain any module configuration parameters?
    thnx

    Hi RajSekhar,
    We have maintained the below modules in the respective comm channels:
    Sender JMS channel:
    ConvertJMSMessageToBinary
    ConvertBinaryToXMBMessage
    MessageTransformBean
    CallSapAdapter
    Note: Maintained the necessary message transform bean module key parameters in the module configuration
    Receiver JMS Channel:
    ConvertMessageToBinary
    SendBinarytoXIJMSService
    Did not alter the by default modules in the Receiver JMS comm channel.
    Am i missing any other configuration.
    Thnx

  • Re-using JMS Receiver Channel

    Hi,
    I have scenarios with SAP -> PI -> 2 Different External Parties.
    External Parties use JMS.
    There are some flows which are common for both the parties, like sending Acknowledgement from SAP to JMS.
    Now can I just configure one common Receiver Communication Channel and Send message (Acknowledgement) to any of the two Parties? So I will have two Receiver Agreements using the same Receiver JMS channel.
    Like by using some concept can I populate JMS channel parameters like IP Address or Server Name , JMS Queue
    Thank you,
    Pankaj.

    Hi,
    You need as many receiver channels as you have JMS queues. When you have 60 JMS queues, then you need 60
    channels.
    I have only 6 queues; one each for one Party.
    When you send all messages to same JMS queues and receiver can identify the message type anyhow, then you need
    only one channel for this queue.
    Ok.
    But even when you have only one JMS queue, you might need seperate channels anyway, for example when you use
    FCC for each interface individually.
    So basically if the setting is different then I need to have that number of channels. the way messages are sent is the same in all the cases. Even when we are using Dynamic Configuration it is the same for all the messages to be send to the External Party.
    Thank you,
    Pankaj.

  • JMS using JBoss !!!

    Hey,
    ich just have a problem realizing jms over the jboss server. Actually, if you want to implement a JMS-Producer or JMS-Consumer you need to define a �*-servie.xml� file which hast to be copied in the deployed directory of the server and it has to be in Classpath off the consumer. So this file hast to be on the client side as well. So, is there a way to put the information of the �-service.xml� in the code of the client, so that it don�t have to be in the classpath any more? I need that for a very special implementation
    kind regards
    Chris

    Hi Javith
    The top three links provided in a Google search 'jboss jms tutorial' look like they'd cover this pretty well -- depending on if you're using JMS inside the JavaEE environment, or your using JMS directly. We might be able to help you more if you were trying to use GlassFish Message Queue and/or GlassFish Enterprise Server.
    Good Luck
    -- Ed

  • Configuring Toplink Cache Coordination using JMS

    After having spent one whole day reading documentation on the above topic, I did not get anywhere. I am looking for a direction to start aquainting myself with Oracle JMS basics to enable me with the configuration in toplink. I hope someone could please help me in getting started, direct me to documentation and/or examples and then I could have some specific and meaningful questions to ask.
    As of now, I have these questions.
    1) In order to configure Toplink Cache Coordination using JMS, do I use Oracle AS JMS or OJMS provider?
    2) Should I be configuring OJMS before I could use Oracle AS JMS?
    3) If I am using Oracle 10.1.2 Application Server, will OJMS Database Schema be defined and the resource adapter deployed by default or is there a way I check this using Oracle Enterprise Manager Console.
    4) Should I be adding a JMS provider within the OC4J for the application I am using before I do any of the above?
    Any help will be highly appreciated.
    Thanks
    Swapna

    Ok. I found my answers
    1) In order to configure Toplink Cache Coordination using JMS, do I use Oracle AS JMS or OJMS provider?
    Either of the one can be used. Here is what I found regarding the trade off
    OJMS and OracleAS JMS are both J2EE 1.3 compliant JMS providers from Oracle. OJMS has been integrated into OracleAS 10g using the JCA adapter while at the same time leveraging Advanced Queuing in the Oracle Database for persistence and recoverability. If database recoverability guarantees, SQL queriability, transparent application failover, message transformation, propagation are required then Oracle recommends using OJMS as the JMS provider.
    OracleAS JMS is a lightweight, in-memory/file based queuing system that provides a complete J2EE 1.3 JMS implementation. It is suited for applications that do not require Oracle specific JMS extensions or the recoverability guarantees that OJMS provides.
    2) Should I be configuring OJMS before I could use Oracle AS JMS?
    No. OracleAS JMS is always provided and preconfigured, except for the topics and queues, with the OC4J installation.
    3) If I am using Oracle 10.1.2 Application Server, will OJMS Database Schema be defined and the resource adapter deployed by default or is there a way I check this using Oracle Enterprise Manager Console.
    No. The schema needs to be created by the admin and OJMS needs to be configured as the JMS Provider using this schema.
    4) Should I be adding a JMS provider within the OC4J for the application I am using before I do any of the above?
    Yes, if not using Oracle AS JMS.
    Hope that was accurate.

  • When using rabbitmq-jms for vFabric RabbitMQ javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card

    When using rabbitmq-jms for vFabric RabbitMQ javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card. I have tested with both 1.0.3 and 1.0.5 clients with RabbitMQ 3.1.5.
    I was wondering if the community was aware of this problem and if there are any workarounds? If not what is the proper channel to file a bug report. An example code snippet is below. The test fails because the TextMessageMatcher expects the destination passed in on construction (second parameter) to equal the desination on the message received (aquired from getJMSDestination).
            Mockery context = new Mockery();
            final MessageListener messageListener = context.mock(MessageListener.class);
            final Latch latch = new LatchImpl();
            final String prefix = "test" + System.currentTimeMillis();
            context.checking(new Expectations() {
                    oneOf(messageListener).onMessage(with(new TextMessageMatcher("MSG1", prefix + ".1234")));
                    will(new CustomAction("release latch") {
                        @Override
                        public Object invoke(Invocation invocation) throws Throwable {
                            latch.unlatch();
                            return null;
            final Connection connection = createConnection(null, null);
            Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
            connection.start();
            Topic wildcardTopic = (Topic) getInitialContext().lookup(prefix + "." + "#");
            Topic destination = (Topic) getInitialContext().lookup(prefix + ".1234");
            final MessageConsumer consumer = session.createConsumer(wildcardTopic);
            consumer.setMessageListener(messageListener);
            MessageProducer producer = session.createProducer(null);
            producer.send(destination, session.createTextMessage("MSG1"));
            latch.await(5000);
            connection.close();
            Thread.sleep(5);
            context.assertIsSatisfied();

    Check where your MDB sends the [response] messages to.

  • Use OC4J jms provider in a java application

    Hi all,
    I'd like to send messages in a OC4J queue (declared in jms.xml) using a java application, is it possible?
    Thank in advice, Cesare
    I read messages by a servlet using this code:
    factory = (QueueConnectionFactory)new InitialContext().lookup("jms/myQueueConnectionFactory");
    queue = (Queue) new InitialContext().lookup("jms/myQueue");
    connection = factory.createQueueConnection();
    connection.start();
    QueueSession queueSession = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    QueueReceiver receiver = queueSession.createReceiver(queue);
    Message message = receiver.receive();

    hi
    if you wish to know how to send and recieve messages from a queue then there is a sample application available at the following link.
    http://otn.oracle.com/sample_code/tech/java/oc4j/samplesPage.html
    try the ch19 sample.
    hope this helps
    regards
    shrinivas

Maybe you are looking for

  • Fields under the tab Goods Receipt in process order.

    Hello Experts, While creation of process order, the fields under the tab 'Goods Receipt' are disabled and already checked. Fields are 'Goods Receipt' and 'Goods Receipt, Non-Valuated'. Fields are 'WEPOS' and 'WEUNB' accordingly. Whereas when we creat

  • Stopped printer please help

    I did some printing and stopped the printer as it was printing.Now I can't get it to start again. I've reset the printer after trying everything i could think of but it still won't work. Help me please I'm at my wit's end! Teresa

  • Cannot export query output when using UNION ALL

    Hi I can run a query in SQL Developer 1.5.5 and if it's a SELECT statement it works fine, but if I output the result of several SELECT statements using UNION ALL after some 10,000 records the SQL Developer crashes and it generates a file whose size i

  • Inbound delivery without PO reference - How to create?

    How can we create an Inbound delivery without referencing a PO?

  • ABAP API - MDM Workflow execute

    Hi, Do we have any methods/function modules available to access MDM Workflow using ABAP API? I have checked through the 19 tutorials of MDM ABAP API available at service.sap.com but was not successful. Regards, Subramanian V.