JMS adapter config for Sonic MQ Failing

Hi
I am trying a simple scenario using JMS adapter with Sonic MQ. The deployment is thru using SDM and Sonic_Client.jar ( JMS client library ) is deployed.
However activating the adapter fails to initialise it. In adapterframework , i get Vague messages saying "Receiver Channel. Details: null" which doesnt help to troubleshoot . The same happens for Sender channel as well.
Any pointers on how to troubleshoot wud be great ! log files !!??
Thanks
Saravana

Hi,
I had similar problem , when I started off with the same scenario. You need to delete the files under javax/jms and create a new .sda acrhive and load it thru SDM.
You should be all set .
Good Luck,
Narendra

Similar Messages

  • Sender JMS adapter configuration for IBM MQSeries

    Dear All,
    i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
    i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
    in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
    1. Transport Protocol: Websphere MQ - is it okay?
    in JMS provider settings:
    2. in channel name - what should be there?
    3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
    4. JMS Complaint - whether WebsphereMQ or JMS API.
    in JMS Settings:
    5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
    6. JMS Message Selector - what data to take here.
    So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
    Regards,
    Rajeev Gupta

    Hi Swaroop,
    you can send me those documents at my gmail-id : [email protected]
    Hi All,
    one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
    Why Channel name is required in JMS configuration data?
    Thanks,
    Rajeev Gupta

  • JMS Adapter Config issues with Plan.xml

    Hi All,
    I'm learning how to configure JMS Resources in WLS to use within a JMS adapter in my application. My approach so far has been :
    1. Configure Outbound Connection in JMS Adapter : eis/wls/Queue. I used the weblogic.jms.XAConnectionFactory as the Connection Factory.
    2. Create Queue within SOAJMSModule : jms/MyQueue and target - soa managed server.
    Updated the JMSAdapter.rar deployment and restarted the SOA server as well as the JMS module.
    3. Create JMS Adapter within JDeveloper to use jms/MyQueue as the destination and eis/wls/Queue as the JNDI source.
    On deployment and running, I see this following error. Apologies it is a bit difficult to trawl through. I did have a look in the Plan.xml and it definitely has an entry for this Adapter and the jndi-name. Any other approach?
    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 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(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 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. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) 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(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:765) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:305) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:276) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source) at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: 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 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(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 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. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:992) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 81 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(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 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. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1012) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:803) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 84 more
    The deployment plan reads as follows :
    <deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
    <application-name>connectors</application-name>
    <variable-definition>
    <variable>
    <name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
    <value>eis/wls/Queue</value>
    </variable>
    <variable>
    <name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
    <value>weblogic.jms.XAConnectionFactory</value>
    </variable>
    </variable-definition>
    <module-override>
    <module-name>JmsAdapter.rar</module-name>
    <module-type>rar</module-type>
    <module-descriptor external="false">
    <root-element>weblogic-connector</root-element>
    <uri>META-INF/weblogic-ra.xml</uri>
    <variable-assignment>
    <name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
    <xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/jndi-name</xpath>
    <origin>planbased</origin>
    </variable-assignment>
    <variable-assignment>
    <name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
    <xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/connection-properties/properties/property/[name="ConnectionFactoryLocation"]/value</xpath>
    </variable-assignment>
    </module-descriptor>
    <module-descriptor external="false">
    <root-element>connector</root-element>
    <uri>META-INF/ra.xml</uri>
    </module-descriptor>
    <module-descriptor external="true">
    <root-element>wldf-resource</root-element>
    <uri>META-INF/weblogic-diagnostics.xml</uri>
    </module-descriptor>
    </module-override>
    <config-root>E:\oracle\product\middleware\11.1.1\soa_11.1\soa\connectors\plan</config-root>
    </deployment-plan>
    Thanks
    JB
    Edited by: 939260 on Jun 20, 2012 5:13 AM

    Hi JB,
    Please follow the below steps from beginning...
    1. Create the JMS Server in the Admin Console, the target server for the same should be the soa server
    2. create new JMS Module.
    3. Create new Connection factory in resources, give your JNDI names, the target servers should be the admin and the soa.
    4. create new queue, give the JNDI names, the target server should be the JMS Server which you have created in the step 1 above.
    5. Now go to deployments, slect the JMS adapter, click update, and say redeploy with the location of JMS-plan.xml given below...
    6. Now inside the composite while configuring the JMS adapter, select the queue which you have created above.
    If you have followed the abpve steps correctly, you should not face any problem.
    Hope this helps,
    N

  • JMS adapter settings for response to dynamic queue

    Hello,
    We are sending a message through JMS to SAP in a synchronous manner (client waiting for the reply after sending the request). The SAP is receiving and processing the message.
    We configured the JMS Sender & Receiver channel as per solution given in SDN for the quetion. ( (2.8) Does the JMS Adapter support the JMSReplyTo feature? )
    1. In Sender communication channel, checked the "JMS Message ReplyTo Destination" attribute  of 'Adapter specific message attributes'
    2. In Receiver communication channel, added the "JMS.Message.DynamicDestination" parameter and value 'true' (without quotes for both strings) in "Set JMS Additional Parameters" table
    3. Added the "JMSReplyTo" header syntax in input xml message as below:
                        a. Message : <?xml version="1.0" encoding="UTF-8"?>
                                 <ns0:getEmployeeInfo xmlns:ns0="namespace">
                                 <employeeId>0000001</employeeId>
                                 </ns0:getEmployeeInfo>
                        b. Destination = com.someDestination
                        c. JMSReplyTo= com.someReplyQueue
    We have selected Transport protocol option "Access JMS Provider Generically"
    But it is not able to send the reply to replyTo destination of the message.
    Wondering if there is anything in the JMS Adapter setting like reply to Destination (technical term DCJMSReplyTo) which can be set to reply queue of the message (to a dynamic destination).
    Please let me know in case anybody knows about the same.
    Thanks & Regards,
    Jayashri Rade

    Refer: http://docs.oracle.com/cd/B14099_19/integrate.1012/b25307/adptr_jms.htm
    •The JMS API specifies three types of acknowledgments that can be sent by the JMS publisher:
    ◦DUPS_OK_ACKNOWLEDGE, for consumers that are not concerned about duplicate messages
    ◦AUTO_ACKNOWLEDGE, in which the session automatically acknowledges the receipt of a message
    ◦CLIENT_ACKNOWLEDGE, in which the client acknowledges the message by calling the message's acknowledge method

  • JMS adapter error for FILE - XI - WebSphere MQ

    Hi
    We are facing an issue for a File to websphere MQ (5.3) implementation.
    When we run the interface , it is giving an error in the run time work bench , Adapter error:
    Exception caught by adapter framework: null
    Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
    Would also like to know if we need to mention  Channel Name while configuring the adapter.
    we have already placed the required driver for WebSphere MQ in XI server i.e com.ibm.mq.jar , com.ibm.mqjms.jar ,com.ibm.mqbind.jar

    Hi John,
    If you are working with IBM MQ 5.3, you would also need connection.jar deployed in the JMS driver.
    You can mention the MQ channel name in the Receiver channel configuration in XI.
    Ensure that the listener service on this channel is started.
    More info at Re: XI--WebSphereMQ : Receiver Channel Inactive in MQ
    regards,
    Paparao

  • Sender mail adapter config for MS Exchange Server

    Dear All Gurus,
    Need your advice on configuring sender mail adapter (mail to file scenario ) for exchange server. I have read a lot of SCN threads and other articles and was not able to find the exact solution for this. PI version : 7.3.
    Thank you all in advance...

    Hi,
    please check the below links.
    http://wiki.scn.sap.com/wiki/display/XI/Step+by+Step+Mail+To+File+Scenario  -  Mail to File
    http://www.riyaz.net/sap/xipi-configuring-the-sender-mail-adapter/90/
    Regards
    srinivas

  • Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ

    Hi,
    I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
    I have updated the oc4j-ra.xml with the following inputs:
    <connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
              <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
              <config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
              <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
              <config-property name="isTopic" value="false"/>
              <config-property name="isTransacted" value="true"/>
              <config-property name="username" value="admin"/>
              <config-property name="password" value="welcome"/>
         </connector-factory>
    But while testing the BPEL process, I get the error:
    <remoteFault>
    <part name="code" >
    <code>null</code>
    </part>
    <part name="summary" >
    <summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
    </part>
    <part name="detail" >
    <detail>null</detail>
    </part>
    </remoteFault>
    Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
    Thanks,
    Jayatu

    I am experiencing the exact same issue while configuring for Tibco EMS!!!
    I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

  • ORABPEL-12141 JMS Adapter

    BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
    Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
    Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
    Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
    XML file entry for JMS Adapter in BPEL :-
    <connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
    <config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
    <config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
    <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
    <config-property name="isTopic" value="true"/>
    <config-property name="isTransacted" value="false"/>
    <config-property name="username" value=""/>
    <config-property name="password" value=""/>
    </connector-factory>
    Portion of Domain.log file :-
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
    <2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
    <2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
    ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
    at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
    at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
    at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
    at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
    ... 16 more
    Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
    ... 21 more

    BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
    Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
    Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
    Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
    XML file entry for JMS Adapter in BPEL :-
    <connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
    <config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
    <config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
    <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
    <config-property name="isTopic" value="true"/>
    <config-property name="isTransacted" value="false"/>
    <config-property name="username" value=""/>
    <config-property name="password" value=""/>
    </connector-factory>
    Portion of Domain.log file :-
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
    <2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
    <2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
    ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
    at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
    at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
    at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
    at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
    ... 16 more
    Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
    ... 21 more

  • Sensors in BPEL (JMS Adapter)

    Hi there! I'm trying to send Sensor-Data into a MQQueue, but this always results in an
    error. The results are in the following Error-Log (sorry, some messages are german but the
    messages are nearly equal to english):
    Caused by: ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Instanziieren von Connection Factory nicht möglich. JMS-Adapter konnte Connection Factory com.ibm.mq.jms.MQQueueConnectionFactory weder JNDI nicht finden noch als Java-Klasse instanziieren
    Weitere Informationen hierzu finden Sie in der Log-Datei.
         at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:207)
         at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:98)
         at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:191)
         at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:132)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:426)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:417)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:380)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:104)
         at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
         at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:125)
         at com.collaxa.cube.engine.sensor.sa.publisher.JMSAdapterPublisher.publish(JMSAdapterPublisher.java:277)
         at com.collaxa.cube.engine.sensor.sa.FilteredDataPublisher.publish(FilteredDataPublisher.java:99)
         at com.collaxa.cube.engine.sensor.sa.BpelPublisher.publish(BpelPublisher.java:129)
         ... 83 more
    Caused by: javax.naming.NameNotFoundException: com.ibm.mq.jms.MQQueueConnectionFactory not found
         at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
         at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:257)
    The following Steps were made:
    - I added two library-paths in the application.xml (D:\Programme\SOA_Suite\10.1.3.1\OracleAS_1\j2ee\oc4j_soa\config\application.xml)
    <library path="../../home/lib/com.ibm.mq.jar"/>
    <library path="../../home/lib/com.ibm.mqjms.jar"/>
    - In the oc4j-ra.xml (D:\Programme\SOA_Suite\10.1.3.1\OracleAS_1\j2ee\oc4j_soa\application-deployments\default\JmsAdapter\oc4j-ra.xml)
    a new connector-factory was added
         <connector-factory location="eis/mqseries/Queue" connector-name="Jms Adapter">
              <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
              <config-property name="factoryProperties" value="QueueManager=MQ_TEST;TransportType=1;HostName=10.1.1.1;Port=1414;Channel=SYSTEM.DEF.TEST"/>
              <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
              <config-property name="isTopic" value="false"/>
              <config-property name="isTransacted" value="true"/>
              <config-property name="username" value=""/>
              <config-property name="password" value=""/>
              <connection-pooling use="none">
              </connection-pooling>
              <security-config use="none">
              </security-config>
         </connector-factory>
    I assume I have to enter a new JNDI-Entry somewhere but the JNDI-Browser in the Application Server is readonly.

    There are two ways to get data into BAM. There is the ADC web service that BPEL uses and then there's Enterprise Link which is the ETL tool that can grab data from Databases and other sources. I only used EL for jms and for ETLing data into a a BAM data object, I never used it for real time. The only real time BAM I've done is with BPEL projects with BAM sensors. I don't think EL is sophisticated enough for looking for changes in rows of data.
    Maybe you can have a db trigger that publishs the changed data to table specially designed for your task. Then you can create an EL "Plan" that runs periodically at a high enough rate that it appears to be in real time in BAM.
    Another possibility is to have the db trigger fire off an xml message that contains the data to the BAM ADC webservice. The BAM ADC web service is http://server:port/OracleBAM/Services/DataObject/DataObjectOperations.asmx.
    It has documentation on how to use it. I don't know if you're db can execute application code or not though.

  • J2SE Adapter Engine / JMS Adapter

    We need to connect to MQ Series 5.3 (Websphere MQ) from the XI (3.0 SP16) box.
    1)Is J2SE adapter engine needs to be enabled/configured in order to use JMS Adapter? Cant we use J2EE JMSAdapter instead of J2SE JMS Adapter?
    2) Where can I download the JMS Adapter libraries, for installation?
    Ours is unix-based installation.
    I have gone thru the thread
    Installation and then Configuration of Plain J2se Adapter Engine
    and the SAP Note: 747601 that talks about J2EE JMSAdapter MQSeries libraries.
    TIA,
    Steve

    Hi Steve,
    Check these ~
    http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
    J2Se adapter
    Installation and then Configuration of Plain J2se Adapter Engine
    Hope this helps,
    Regards,
    Moorthy

  • Restrict message volume through JMS adapter (not individual message size)

    Hi, does anyone know of a way to restrict the flow of messages through a JMS adapter? For example, If I wanted to only allow up to 1000 messages to be sent in an hour to a particular system. The rest should just be queued in the Adapter Engine until the next hour begins in order to smooth out the load on the recieving system.
    I know this is poor design but there is a system that is getting overwhelmed and cannot be easily changed right away. I'd like a way to control this from the middleware using standard PI (no ccBPM).
    Any ideas?
    Thanks in advance,
    Aaron

    Stefan, thank you for the idea, that is a good one.
    I'm going to assume there is nothing specific we can do in the SAP JMS adapter to control the flow, and look to a solution in the queueing software like you suggested or the 3rd party application.
    -Aaron

  • JMS Adapter Testing

    Hi Team
    I am using the JMS adapter as a sender and the idoc as receiver. i want to test the  End to End scenario. i am using the Transport Protocol as " Access JMS Provider with JNDI".
    I have been provide by a program which helps to write the xml message into the queue.
    My doubt is how to run this program and where to run this java program??
    this is the first time i am developing scenario by using the JMS adapter
    Awaiting for your replies
    thanx

    Hi,
    Are you trying to test the scenario JMS -> PI ?
    If you are trying to add a message to the queue, you can use MQ client software to do this - this allows you to connect to a remote queue manager and add messages to any queue on the queue manager.
    Cheers
    Colin.

  • XI JMS adapter after JMS provider reboot

    Hi All,
    I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.
    After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.
    In JMS adapter we have folloving settings and we are connected straight into queue:
    Transport Protocol = SonicMQ JMS Provider
    General JMS Settings:
    Transactional JMS Session is in use
    Delivery Mode of Message Producer = Persist JMS messages..
    + Queue user & pw
    Error Handling Settings:
    Wait After Message Error(msecs) = 60000
    Wait Before Reconnect(msecs) = 60000
    Does anyone ran into this earlier?
    Thanks in advance.
    -Kimmo

    Hi Saravana,
    It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory
    It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.
    We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.
    We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.

  • JMS Adapter troubleshooting

    Hello,
    I have a JMS adapter configured for MQ and can get messages to / from it. However, in troubleshooting with the MessageTransferBean my messages seem to dissappear into the JMS ether
    How can I see the contents and more detailed error messages for the JMS adapter in XI/PI? Runtime Workbench shows only a portion of the error and I can't figure out where to find the rest.
    Any advice on how to monitor the SAP JMS layer and see helpful troubleshooting logs are greatly appreciated!
    Many thanks,
    Aaron

    Hi Aaron,
    I am giving you all the chapters from the bible of jms adapters.
    1)notes for JMS adapter
    Go thru these notes 790963,747601,746393,856346,802754,
    837501 and 790224.
    2)information regarding use of JMS Adapters,Go thru these links of help.sap.com
    JMS Adapter:
    http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
    Configuring the Sender JMS Adapter:
    http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
    Configuring the Receiver JMS Adapter:
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
    JMS-Provider-Specific Settings:
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
    And to deploy the jars which are given in the JMS Adapter link go thru this article "How To Install and Configure External
    Drivers for JDBC and JMS Adapters"
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60237e74-ef19-2b10-5a9b-b35cc6a28e83
    http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Regards
    joel
    Edited by: joel trinidade on Mar 26, 2009 11:22 AM

  • MDB,MDB container or JMS adapter stops processing messages from JMS queue

    Hi guys,
    we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
    The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
    Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
    Thanks for your help.
    Cheers,
    Martin
    Edited by: east1979 on Jan 13, 2009 8:06 AM

    Hi Manoj,
    I have a very similar if not identical issue,
    Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
    15/11/12 09:10:08  JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
    TION TO CONTINUE.
    15/11/12 09:10:15  Communication Error. See real time job log for details.
    Dump available:
    https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
    Version of DS:14.0.3.273
    Any comments?
    Thansk and kind Regards,
    Kenneth

Maybe you are looking for

  • How can I pair Firefox browser intalled on Android tablet with my TV?

    My TV is connected to my home network internet through Smart Hub on Samsung Blu-ray. The Smart Hub has its own browser which is very slow and can not be paired with my Android tablet. I could pair YouTube with YouTube/pair though ! I tried to downloa

  • Getting Data from SAP ECC & BI to Crystal Reports and then Broadcasting.

    Hi, I need to get the data from SAP ECC & BI to Crystal reports and then after formating data in Crystal reports, my requierment is to send via email (Broadcasting). Is there any option to  Broadcast from Crystal reports? I read Ingo Hilgefort blogs,

  • My screens disappear to left or right  & double sign in on lion OSX 10.8.3

    Can any one help me ? When I Mac boots or wakes from slpeep it shows 2 sign in screens  thats problem #1 EVEN if i ignore  one  i get on. #2 is  Ill be typng and move my mouse to the left ofr right in center of screen and my document disapeers. I use

  • Cleaning Up "Untitled Audio" Files

    I used to not name a project until after i'd recorded multipe tracks, so over the months i've accumulated a lot of "untitled audio" tracks numbered from 1-300 or so. Is there any way to see which files were used for which song so I can properly renam

  • SPM 3.0 GA

    Hi, When SPM 3.0 is going to be in General Availability. What is the experience of SPM 3.0 with ramp up customers. Pls sha