Query regarding durable subscribers in JMS Adapter (11g)

Hi , I am facing some issue with using durable subscribers..
I am doing a POC in which I have two consumers (consumer 1 and consumer 2) listening to a topic.
On the server console, the monitor tab of the JMS topic shows number of consumers as 2 which is good.
Also, when any message is put on the topic , BPEL processes for both consumers get triggered as expected.
Now, I add durable subscriber ID as 123 to one of the consumers (consumer 1)
After deploying the code, the count for the number of current consumers listening becomes 1.
So I create a durable subscriber on the console with id as 123 after which the consumer count is back to 2.
The issue however is that, now when I put a message on topic , only consumer 2 is triggered.
The message for consumer 1 can be seen on the durable subscriber 123's page.
My question is that, since the consumer is listening to the topic then why is the message going to the subscriber instead of creating instance ?
I also tried following :
1. created a new outbound connection pool in the resource adapter
2. setting property FactoryProperties to value "ClientID=123"
3. pointing the adapter connection factory to this new location
but this is also not helping.
Could anyone please help me out in this ?
Thanks and Regards,
Ketan

did u have any luck? can u tell me steps

Similar Messages

  • Durable Subscribers in JMS

    Hi ,
    I need to set the Durable Subscriber in JMS using BPEL.
    what are the configurations ,I need to set in the Jdeveloper.
    If any one having idea , please share your ideas.
    Thanks in advance
    Shyam

    Hi
    You can set the Durable subscriber through wizard. When you configure the JMS adapter at Step 6 it asks for the Durable Subscriber. Just write the name of subsriber (it should be same as was set in JMS queue)
    Let me know if you further have any query
    Regards
    Sahil

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

  • Regarding Module Configuration of JMS Adapter

    Hi,
         Now i am working on IDoc to JMS interface, I am facing complexity in creating the structure in Module tab of Receiver JMS Adapter. Because the target system is expecting fixed length file so i should  use the Local EJBs available in Module tab of Receiver JMS adapter and i need to pass the fieldFixedLegth parameters for all the nodes coming from DELVRY01 Idoc.  I think creating structure for all the nodes in receiver jms adapter is so complex, If you are having any other alternatives, please share with me.
    The below is the IDoc xml which is coming from source side.
       <?xml version="1.0" encoding="UTF-8" ?>
    <DELVRY01>
    <IDOC BEGIN="1">
    <EDI_DC40 SEGMENT="1">
    <TABNAM>EDI_DC40</TABNAM>
      <MANDT>100</MANDT>
      <DOCNUM>000000000999999</DOCNUM>
      <DOCREL>1145</DOCREL>
      <STATUS>1</STATUS>
      <DIRECT>1</DIRECT>
      <OUTMOD>2</OUTMOD>
      <IDOCTYP>DELVRY01</IDOCTYP>
      <MESTYP>abcde</MESTYP>
      <SNDPOR>efghi</SNDPOR>
      <SNDPRT>LS</SNDPRT>
      <SNDPRN>LMNOP100</SNDPRN>
      <RCVPOR>A000000023</RCVPOR>
      <RCVPRT>LS</RCVPRT>
      <RCVPRN>TB</RCVPRN>
      <CREDAT>20056556</CREDAT>
      <CRETIM>183734</CRETIM>
      <SERIAL>12345678</SERIAL>
      </EDI_DC40>
    <E1EDL20 SEGMENT="1">
      <VBELN>006456451</VBELN>
      <VSTEL>4656</VSTEL>
      <VKORG>1665</VKORG>
      <ABLAD>ABCDEDFJSDFDF</ABLAD>
      <ROUTE>DFSDF</ROUTE>
      <VSBED>08</VSBED>
      <BTGEW>3.000</BTGEW>
      <NTGEW>333.000</NTGEW>
      <GEWEI>NNN</GEWEI>
      <VOLUM>450.190</VOLUM>
      <VOLEH>DMBG55TERTQ</VOLEH>
      <ANZPK>00000</ANZPK>
      <XABLN>0001995346331</XABLN>
      <LIFEX>N</LIFEX>
    <E1EDL22 SEGMENT="1">
      <VSTEL_BEZ>ABCDEFGHIIJFLD</VSTEL_BEZ>
      <VKORG_BEZ>SDFKJSDFSDF</VKORG_BEZ>
      <ROUTE_BEZ>FSDNFKSDJFKJASDKFJSDJFL</ROUTE_BEZ>
      <VSBED_BEZ>FNSDKFSD,F,MSDF,</VSBED_BEZ>
      </E1EDL22>
    <E1EDL21 SEGMENT="1">
      <KDGRP>10545</KDGRP>
      <BEROT>teGHGHst FGHHFGHXI </BEROT>
      <TRAGR>0001</TRAGR>
    <E1EDL23 SEGMENT="1">
      <LFART_BEZ>Outbound delivery</LFART_BEZ>
      <KDGRP_BEZ>LPHG Wholesale</KDGRP_BEZ>
      <TRAGR_BEZ>On HHFH</TRAGR_BEZ>
      </E1EDL23>
      </E1EDL21>
    <E1EDL18 SEGMENT="1">
      <QUALF>ORI</QUALF>
      </E1EDL18>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>AG</PARTNER_Q>
      <PARTNER_ID>00000GHF12889</PARTNER_ID>
      <LANGUAGE>EN</LANGUAGE>
      <FORMOFADDR>Makro SA</FORMOFADDR>
      <TELEPHONE1>041 3600TERTE605-C...</TELEPHONE1>
      <TELEFAX>041 36006TRT47</TELEFAX>
      <COUNTRY1>ZHFGHA</COUNTRY1>
      <REGION>EHGHC</REGION>
    <E1ADRE1 SEGMENT="1">
      <EXTEND_Q>100</EXTEND_Q>
      <EXTEND_D>6HG15FGHFG05006416</EXTEND_D>
      </E1ADRE1>
      </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>WE</PARTNER_Q>
      <PARTNER_ID>00000178E87T</PARTNER_ID>
      <LANGUAGE>EN</LANGUAGE>
      <FORMOFADDR>Makro SA</FORMOFADDR>
      <NAME1>Makro Port Elizabeth Br 14</NAME1>
      <NAME3>t/a Makro SA</NAME3>
      <STREET1>CDFJSDLFJLS d</STREET1>
      <COUNTRY1>ZFSDFA</COUNTRY1>
      <REGION>EFSDFC</REGION>
    <E1ADRE1 SEGMENT="1">
      <EXTEND_Q>100</EXTEND_Q>
      <EXTEND_D>6001534453505006416</EXTEND_D>
      </E1ADRE1>
      </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>54OSP</PARTNER_Q>
      <PARTNER_ID>404534501</PARTNER_ID>
      <LANGUAGE>EN</LANGUAGE>
      <COUNTRY1>Z5454A</COUNTRY1>
      </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>OSO</PARTNER_Q>
      <PARTNER_ID>1054400</PARTNER_ID>
      <COUNTRY1>Z5453A</COUNTRY1>
      </E1ADRM1>
    <E1EDT13 SEGMENT="1">
      <QUALF>006</QUALF>
      <NTANF>2005455470706</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>2005453470706</NTEND>
      <NTENZ>00053454000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00005340000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>003</QUALF>
      <NTANF>20070706</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>200705345706</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000053455400</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>001</QUALF>
      <NTANF>20070706</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>20070706</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>007</QUALF>
      <NTANF>20070709</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>20070709</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>010</QUALF>
      <NTANF>20070705</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>20705</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDL28 SEGMENT="1">
      <ROUTE>ED545S1</ROUTE>
      <DISTZ>0.000</DISTZ>
    <E1EDL29 SEGMENT="1">
      <ROUTE_BEZ>FKLSDJFLSJDFJSDFJLSDJFLKSD</ROUTE_BEZ>
      </E1EDL29>
      </E1EDL28>
    <E1EDL24 SEGMENT="1">
      <POSNR>000010</POSNR>
      <MATNR>000000000000</MATNR>
      <MATWA>000000000</MATWA>
      <ARKTX>OmFDFS 2kg.</ARKTX>
      <MATKL>FSD5345FSDFLAUND</MATKL>
      <WERKS>10FDF40</WERKS>
      <LGORT>01</LGORT>
      <LFIMG>10545.000</LFIMG>
      <VRKME>C54T</VRKME>
      <LGMNG>10553545.000</LGMNG>
      <MEINS>CT534555345545345</MEINS>
      <NTGEW>1653454.000</NTGEW>
      <BRGEW>181.000</BRGEW>
      <GEWEI>KGM</GEWEI>
      <VOLUM>450.190</VOLUM>
      <VOLEH>DMQ</VOLEH>
      <LADGR>0534543002</LADGR>
      <TRAGR>0001</TRAGR>
      <VKBUR>UF53401</VKBUR>
      <VKGRP>160</VKGRP>
      <VTWEG>00</VTWEG>
      <SPART>00</SPART>
      <GRKOR>000</GRKOR>
      <EAN11>16001085031034</EAN11>
      <POSEX>000000</POSEX>
    <E1EDL25 SEGMENT="1">
      <LGORT_BEZ>Main s53453453454tore</LGORT_BEZ>
      <LADGR_BEZ>Forklift</LADGR_BEZ>
      <TRAGR_BEZ>On pallets</TRAGR_BEZ>
      <VKBUR_BEZ>Gener534534al Trade</VKBUR_BEZ>
      <VKGRP_BEZ>RSM E534 Cape</VKGRP_BEZ>
      <VTWEG_BEZ>FKLSDFKLS</VTWEG_BEZ>
      <SPART_BEZ>FSDFSDFJoducts</SPART_BEZ>
      </E1EDL25>
    <E1EDL26 SEGMENT="1">
      <PSTYV>TAN</PSTYV>
      <MATKL>FGUND</MATKL>
      <PRODH>0125VH</PRODH>
      <UMVKZ>1</UMVKZ>
      <UMVKN>1</UMVKN>
      <KZTLF>B</KZTLF>
      <UEBTO>0.0</UEBTO>
      <UNTTO>0.0</UNTTO>
      <KVGR1>Z4FDFSDFSD</KVGR1>
      <KVGR2>TPS</KVGR2>
    <E1EDL27 SEGMENT="1">
      <PSTYV_BEZ>Standard Item</PSTYV_BEZ>
      <PRODH_BEZ>OmoFFD Regular 8X2kg.</PRODH_BEZ>
      <WERKS_BEZ>ConFSDFgella DC</WERKS_BEZ>
      <KVGR1_BEZ>PE Cust Del</KVGR1_BEZ>
      <KVGR2_BEZ>rd party sales</KVGR2_BEZ>
      </E1EDL27>
      </E1EDL26>
    <E1EDL43 SEGMENT="1">
      <QUALF>C</QUALF>
      <BELNR>FDF</BELNR>
      <POSNR>000010</POSNR>
      <DATUM>FFSDF</DATUM>
      </E1EDL43>
    <E1EDL41 SEGMENT="1">
      <QUALI>54</QUALI>
      <BSTNR>test I Link</BSTNR>
      <BSTDT>00000000</BSTDT>
      <POSEX>000010</POSEX>
      </E1EDL41>
      </E1EDL24>
      </E1EDL20>
      </IDOC>
      </DELVRY01>

    not related

  • JMS Adapter 11g

    hi All,
    I am using SOA/JDev 11.1.1.1.0
    I created a queue in jms and i am trying to produce a message to taht.
    But I am getting below error.
    +<fault>+
    +<faultType>0</faultType>+
    +<bindingFault>+
    +<part name="summary">+
    +<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. JMSProducer:Producer [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='jms/R7DevQueueCF'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to jms/R7DevQueueCF. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>+
    +</part>+
    +<part name="detail">+
    +<detail>JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='jms/R7DevQueueCF'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to jms/R7DevQueueCF. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server </detail>+
    +</part>+
    +<part name="code">+
    +<code>null</code>+
    +</part>+
    +</bindingFault>+
    +</fault>+
    I tried with exact connection factory and default connection factory.
    But still i am getting the same.
    Please help me out.
    Regards
    PavanKumar.M

    Have you tried cross-domain security or domain trust?

  • How to remove header data from JMS Queue while sending by jms adapter

    Hi.
    I have a problem regarding the MQ-series JMS adapter.
    When writing the file the JMS adaptor putting  some additional tags.
    Actually we are converting idoc-xml to flat file by using ABAP mapping which is available in SAP document. We are using JMS Receiver adapter, whiel sending flat file to JMS QUEUE,  it is displaying some extra xml tags. I think this is the header data available in IDoc XML. Can any body help me in removing header data.
    There must be some way for XI's JMS adaptor to not include these information.
    My example looks like this:
    RFH Ø  
    ¸MQSTR
    ¸ " is junk that I really dont need in the file.
    How can you setup the JMS adaptor not to put in these information?
    Thanks & Regards,
    Madhusudhan

    not related

  • Calling Foreign JMS in SOA Suite 11g JMS Adapter

    Hi,
    Just want to get some guidance in the implementation of Foreign JMS in WebLogic 10.3.
    I followed the creation of the Foreign JMS Server using this document:
    http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignServers.html
    I am trying to connect to a remote Weblogic 10.3 JMS queue but cannot get pass the JDev wizard stage.
    I need to call the foreign JMS via the Fusion 11g JMS Adapter but cannot lookup the destination from the JDev wizard. My composite will produce a message that will end up in the remote queue.
    Has anybody got this to work? Is this supported in JMS Adapter? I've read quite a few using MDB to call the Foreign JMS but not JMS Adapter.
    Regards,
    Robert

    Please refer to the following document that shows how to access remote wls jms queues and topics. This is the preferred way when accessing remote wls destinations.
    http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
    Thanks
    Aman

  • 10g AQ Adapter converting to 11g JMS Adapter

    Hi,
    I'm looking for any documentation that shows how to migrate a project/application from using 10g AQ Adapter to 11g JMS Adapter.
    Thanks,
    Bruce

    Hi Anuj,
    I am new to SOA 11g.
    I followed the steps mentioned in the URL which you have given.
    I created the jms module and added a foreign server to it while configuring the foreign server it asks for the JNDI Connection URL and i have no clue what
    value should be there in this field.
    Do i need to create a jndi connection URL for my database where i have created the queue?
    Sorry if i am sounding silly but it will be great if you can elaborate on this.
    With Regards,
    Harshwardhan

  • Non-durable subscribers persists after the end of their JMS session

    Hi all,
    I'm using OAQ as my JMS Provider.
    I have created code for publishing and recieving messages to/from topics. Messaging works fine, but I have one problem:
    All my non-durable subscribers persists after the end of their JMS session. I always perform unsubscribe operation in code and then closing session and connection.
    When I subscribe to topic, there's one more line in DB table ( etc. NAME: TSUB_1_24E6DB98A2EB7712E040A8C, TYPE: 65). I have expected that subscribers will be deleted after performing unsubscribe operation, but they don't...
    Can you help me with this problem? Thanks for any answer.
    Best Regards,
    Juraj

    Have you found a solution to this yet - because I face the same problem

  • SOA Suite 11g - dynamic JNDI destination JMS adapter

    hi there soa suite users,
    im currently using oracle soa suite 11g,
    my use case having a bpel process processing something
    and then route the result to several queue.
    like this:
    jms/adminduk/queue/mks1
    jms/adminduk/queue/pdg1,
    etc...
    so the destination name can be build dynamically in the bpel,
    and i stored in a string variable "destName".
    (im using WLS 10.3 jms)
    now i need to invoke a jms adapter service with produce operation,
    but the queue destination needs to be using the variable "destName".
    i already tried using assigning to property "jca.jms.JMSDestinationName"
    in the invoke activity.
    <invoke ...>
    <bpelx:inputProperty name="jca.jms.JMSDestinationName"
    variable="destName"/>
    </invoke>
    but it seems not working, and im getting this error:
    Caused by: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
    parts: {{
    summary=<summary>Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation
    'SendSinkBioWniFromDaerahResponse' failed du
    e to: ERRJMS_ERR_CR_QUEUE_PROD.
    ERRJMS_ERR_CR_QUEUE_PROD.
    Unable to create Queue producer due to JMSException.
    The invoked JCA adapter raised a resource exception.
    Please examine the above error message carefully to determine a resolution.
    </summary>
    ,detail=<detail>[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer
    requested. The linked
    exception may contain more information about the reason for failure.</detail>
    ,code=<code>null</code>
    this is a basic use case of jms interoperability,
    anyone have answers to this ??
    thank you :)

    Hi,
    If someone is looking to dynamically set the JMSqueue name here is the solution.
    in the Invoke activity set "jca.jms.JMSDestinationName"
    value to "JMSHeaderVariable"
    set the type to "input"
    in the JMSHeaderVariable set the queue name dynamically.
    and in the JMSadapter give any valid queue name, still the message will be routed to the queue which you have set in the invoke adapter.

  • Query: Sender JMS Adapter configuration

    Hi All,
        I'm trying out a scenario which sends data from a Message Queue to SAP.
        For this I need to configure JMS adapter in the sender side. I would like to know whether <b>should I specify any content conversion parameters like "fieldLength" or "fieldSeperator" as we do it in sender file adapter for XI's indivual field identification.</b>
       If no then how the variables will get mapped properly to the XI outbound ( sender ) Structure from Message Queue???..
       Bcoz I believe MQ sends the data as a single stream of characters not as individual field..
       Please advice..
    Regards,
    Joe.
    Message was edited by: Joe

    Hi Satarupa,
              Thanks for your reply.
      But if I'm getting say a stream of 10 characters (Name - 4 characters, Address - 5 characters, Option - 1 character totally 10 characters), how the system will know it has to send first 4 characters to name defined in XI, next 5 characters to Address defined in XI and the next 1 character to Option  if I don't specify the conversion parameters?? 
      Bcoz the data flows in the same way to XI as it flows for file adapter, where we speciy the content conversion parameters which helps it to send it to the variables defined in XI accordingly.
      If you've some docs on both sender and receiver JMS adapters pls. lemme know..
    Thanks,
    Joe.

  • JMS Adapter - SOA Suite 11g

    Hi,
    We are facing a weird issue while configuring JMS adapter for a queue sits on a remote Weblogic JMS Server.
    - Configured adapter in a BPEL process and provided JNDI name 'eis/wls/Queue'
    - Configured outbound connection pool with remote server url/user id/pass
    - added the same jndi name properties in soa/connectors/JMSadapter.rar/weblogic-ra.xml
    When we test the service, the following error is thrown:
    java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. PublishToJms:JmsAdpWrite [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
    Please help...
    Regards,
    AP

    Hi,
    We have re-deployed JMS adapter after changing weblogic-ra.xml as per the product documentation. Now getting a different exception..
    java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: ERRJMS_PROVIDER_ERR. ERRJMS_PROVIDER_ERR. Unable to produce message due to JMS provider internal error. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:570) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:157) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at
    Any thoughts on this ?
    Regards,
    AP

  • Query regarding integrating sun MQ with Oracle SOA suite 11g

    Hi,
    I am new to SOA suite 11g.I have a requirement of connecting to Sun MQ 4.4 queue from Oracle SOA suite 11g.Right now, I have found a work around using java embedding by connecting to the queue from java code directly.Can I use the JMS adapter for this purpose? If yes what are the options of doing that.I saw there is an option of third party queue in the JMS adapter configuration wizard but could not get it to work.Any help is appreciated.
    Thanks in advance

    I think we can exchange only data types, i dont see any data type which can hold the object types.
    If you find anything better let us know.
    Constructing string xml and converting to xml is best option i can think of.
    Thanks,
    Vijay

  • Query regarding JMS MQ drivers in XI

    Hi All,
    Is it possible to run JMS adapter with MQ version 6.0 in an environment where the JMS drivers available is of MQ 7.0 .
    Regards,
    Yogesh

    Hi,
    As per the SAP Note 1086303 - XI JMS Adapter and IBM Websphere MQ: FAQ
    12)What is the recommended version of MQ drivers for the PI JMS Adapter - IBM MQ connectivity ?
    Answer:
    MQ Client Libraries are backward compatible with all supported IBM Websphere MQ Server versions. However, we strongly advise you use the highest version of the MQ client libraries by downloading the latest server version from the IBM site and then extracting the client libraries for the specific MQ version as specified in SAP note 747601. The link to the latest MQ Client libraries is :  "http://www.ibm.com/support/entry/portal/Downloads/Software/WebSphere/WebSphere_MQ" .  Kindly then navigate via "Fixes by Version" and select the MQ Client Version in use. It is always recommended to apply the latest APARS for the specific MQ client library version in order to take benefit of the latest known issues.
    Regards,
    Francis

  • JMS Adapter in BPEL 11g

    Hi All,
    i am trying to produce message to JMS QUEUE with the help of JMS Adapter.
    PFB the Details:
    jmsmodule:- NewJMSModule
    Connection Factory :-  jms/newconfactor
    Queue jms/testqueue
    create  
    oracle.tip.adapter.jms.IJmsConnectionFactory :- eis/jms/ajayQueue
    provide location :- jms/newconfactor
    I  am getting below error
    when my jms server target to AdminServer
    Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. JMSProject:JMSQueueInsertion [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141 ERRJMS_CONN_FAC_NOT_FOUND. ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory eis/confac neither through JNDI nor instantiate it as a Java class. Please examine the log file to determine the problem. Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
    when my jms server target to SoaServer
    <part  name="summary">
    <summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: ERRJMS_ERR_CR_QUEUE_PROD. ERRJMS_ERR_CR_QUEUE_PROD. Unable to create Queue producer due to JMSException. Please examine the log file to determine the problem. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
    </part>
    <part  name="detail">
    <detail>[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.</detail>
    Any help is appreciated.
    Regards,
    Ajay

    Hi Ajay,
    It seems that your SCA is looking for a connection factory with the JNDI name "eis/confac" instead of "eis/jms/ajayQueue" which is the one you configured. You should have a "*_jms.jca" file in your project with the following entry: <connection-factory location=" .. . Could you check that it is pointing to the correct JNDI
    best regards, Nicolas

Maybe you are looking for