PI7.1 JMS Adapter - connect to NW6.40

Hello,
We are facing following problem on SAP PI:
We have a scenario where PI (version 7.1) is connecting to another SAP NetWeaver system (version 6.40).  There is an application that reads/puts messages from/to JMS Queues running on this system. PI has to connect the JMS Provider of 6.40 system and read/put these messages from/to these JMS Queues.
This scenario worked fine till we used XI 3.0 (NW6.40). We configured sender JMS channel with link to remote JMS Server and parameter "force_remote".
After installation of new PI7.1 we noticed some issues:
1.the connection is unstable. Sending JMS messages from PI to NW6.40 queue works a while but then we get error like this:
Adapter Framework caught exception: Unable to write new JMS message body for message: 00237d29-13fc-02ed-ba85-01d046631592: ConnectorException: Connector for ConnectionProfile of channel: EON_CC_jms_rcv_omsmessageon node: 922834950 having object id: 70855b1c6c483e869982ea2fe9787b36 was unable to create a new javax.jms.TextMessage message: javax.jms.IllegalStateException: Session is closed.
2. we cannot read messages from JMS Queue of NW6.40 at all. The messages are there in queue, communication channel is running and succesfully connected to queue but no message is processed and no error shows in communication channel monitoring.
Has anybody solve similar problem with connection between 7.1 and 6.40 NetWeaver?
I think the problem can be backward incompatibility of 7.1 SAP JMS libraries against 6.40. If this is true then the question is whether it is possible to deploy old libraries and run them simultaneously with native 7.1 libraries?
Thanks

problem sorted - factory property settings were not configured correctly in JMS Adapter connection pool

Similar Messages

  • Error with the Receiver JMS Adapter (Connection On-Demand feature)

    Hi,
    In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
    Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
    Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
    The message status was set to WAIT.
    Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
    Any idea?
    PI 7.1 EHP1
    Thanks,
    Martin
    /people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
    Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

    Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

  • PI 7.1:  Weblogic (JMS adapter) - Connectivity &  MONITORING!!

    Hi ALL
    WE have a requirement to integrate PI with Weblogic server using JMS adapter.
    However, we would like to host the JMS queues in PI, so that we have end to end monitoring capability.
    We do not want Weblogic Server to host these queue, instead want PI 7.1 to maintain these quese ... so that we can monitor these interfaces end -to- end.
    Please, let us know if anybody has done this Weblogic integration with JMS queue monitoring  within PI 7.1.
    So, the main GOAL is to have JMS Queue monitoring in PI, where we have visibility to how many queues are running and the no.of messages in sent in each queue and failures if any.
    Also, is there any Queue monitoring under /nwa adminstration; where we can see the queue created in PI
    So, if anyone has implemented this in PI 7.1, please let us know.
    Your help is greatly appreicated!!
    Thank you,
    Patrick.
    Edited by: Patrick Jones on Sep 25, 2009 6:24 PM
    Edited by: Patrick Jones on Sep 25, 2009 8:58 PM
    Edited by: Patrick Jones on Sep 26, 2009 12:09 AM
    Edited by: Patrick Jones on Sep 26, 2009 10:04 PM
    Edited by: Patrick Jones on Sep 28, 2009 2:28 AM

    Hi Patrick,
    We've done something similar but with PI 7.0 & Weblogic hosting the queue so I'm not sure how useful this will be to you...
    Firstly, great move to have the queue/s hosted in PI (in my opinion), for several reasons:
    - You won't have to keep investigating whether or not Weblogic actually put the message on the queue/s or not.
    - It makes monitoring a bit easier.
    - For some reason on PI 7.0, when Weblogic or stops the queue services then PI stops polling for messages although we have green lights in RWB communication channel monitoring. If we stop & start the comm channel/s then the JMS Adapter starts picking up messages off the queue. A couple of SAP notes point to a known Weblogic issue with the way Weblogic works with initial contexts. Hosting the queues in PI would take care of this problem.
    Currently we are using HermesJMS to monitor all JMS queue/s with number of messages & possible message backlog in the queues. We are also working on setting up Business Processing Monitoring that can do full end-to-end monitoring of a business process across the landscape not just in within PI. I'm also curious to see what's available in PI 7.1 for JMS queue monitoring.
    Regards, Trevor

  • Jms  Adapter Connection- Deployment Need Help!!!

    Hi,
    a got a problem when i try to deploy a new Jms Connection with JNDI and OpenJms.
    (I use the Visual Administrator-Gui /services/JmsConnection to do this)
    I already deployed my OpenJms Libary jar at xi.
    And i get this error if i want save the JmsConnection.
    Is there something else i must create or import ???
    Would  be great if someone knows this problem???
    Here the error form Xi Visual Administrator:
    java.rmi.RemoteException: Cannot deploy application openjms.sf.net/openjms.app..
    Reason: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.; nested exception is:
         com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
         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:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
         ... 35 more
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
         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:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
         ... 35 more
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:536)     at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)     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:324)     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)     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:94)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
         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:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
         ... 35 more
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
         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:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
         ... 35 more
         at com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException.writeReplace(BaseDeploymentException.java:101)     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:324)     at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)     at javax.management.MBeanException.writeObject(MBeanException.java:126)     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:324)     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)     at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)     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:324)     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)     at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:168)     at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)     at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)     at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1267)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)     ... 9 more

    did you solve this problem. if yes can u pls tell me how. i get the exact problem in Web AS Visual Administrator.
    thanks
    RD

  • Initiate fails in BPEL Console for BPEL process connecting to JMS Adapter

    We have a BPEL process picking up data from JMS Queue of TIBCO EMS server. When we try to run this process from BPEL Console Initiate tab, we get following error dump :
    Oracle BPEL Process Manager Full Cycle
    An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
    Attachments:
    Build Information:
    Oracle BPEL Server version 10.1.3.1.0
    Build: 0
    Build time: Mon May 15 06:39:46 PDT 2006
    Build type: release
    Source tag: PCBPEL_SOABETA_GENERIC_060515.0600
    Exception Message:
    [javax.servlet.ServletException]
    The system encounters errors while running as the authenticated identity.
    Exception Trace:
    javax.servlet.ServletException: The system encounters errors while running as the authenticated identity.
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:416)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:622)
         at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:161)
         at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:50)
         at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:98)
         at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:103)
         at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:395)
         at displayProcess.jspService(_displayProcess.java:857)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:590)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:514)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
         at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:392)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:406)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:622)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
         at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:260)
         at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:50)
         at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:194)
         at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:199)
         at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:131)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
         at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:392)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:406)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:620)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:869)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:449)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:233)
         at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
         at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:847)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Also the BPEL process containing JMS adapter is not able to pick up data from JMS queue.
    The same adapter was used in ESB service as well, which is working fine. There are no issues in ESB JMS Adapter connecting to JMS Queue of TIBCO EMS server.
    Your help is appriciated.

    Try the BPEL / SOA forum, you'll get more help there.
    -steve-

  • Problem with JMS Adapter after upgrade to 7.1

    Hi All,
    After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
    Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
    Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
    Edited by: Luqman on Oct 31, 2008 5:39 PM

    does following JAR files in place in aii_af_jmsproviderlib.sda.
    ●      com.ibm.mq.jar
    ●      com.ibm.mqbind.jar
    ●      com.ibm.mqjms.jar
    ●      connector.jar (use the JAR file from the J2EE client directory)
    can u check n confirm.
    i hopw u have followed the proper deployement process.
    chirag

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

  • Problem testing JMS adapter

    I have create and configure JMS resource but still i am getting this exception
    Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'sendMessage' 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.
    Fault
    BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'sendMessage' 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.
    Kindly help

    This is how I configured
    Configure the JMS Queue Resource (Jndi name=>>> jms/demoMsgQueue)
    Configured the JMS Connection Factory Resource
    configured the demoCF JMS connection factory
    Created a JMS Adapter Connection Pool
    Associate the Connection Pool with the Connection Factory
    Redeployed the JMS Adapter with the New Resources
    How I can do bouning app server?

  • JMS Adapter timeout property

    How do I set timeout property for JMS adapter in BPEL in SOA Suite 10g ?
    Scenario :
    In one of the business scenarios, a JMS message in enqueued to WebLogic JMS queue from BPEL process.
    There is a asyncronus invoke activity to the JMS adapter partner link.
    This invoke activity to the JMS adapter took 15 mins in one of the invocations and hence giving timeout to the bpel client.
    Query :
    Is there any way I could set the timeout for this invocation, either at partner link level or a JMS adapter connection factory level.

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

  • JMS adapter: JNDI not able to connect to TIBCO server.

    Hi All,
    We are facing a strange problem here related to JMS adapter. We are trying to connect to TIBCO using JMS adapter.
    We have 3 different Business Services, all the three using JMS channels. All the JMS channels are connecting to the same server on same port 7222. We have every thing same in all the JMS channels except the Que Name and the queue/log on user.
    All the channels under 1 particular services are working fine while under the other two are giving below error:
    ===========================================
    Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection factoryQueueConnectionFactory, for profile: ConnectionProfile of channel: <Interface name> on node: <server node> having object id:<Object ID>: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to any server at: tcp://<host1>:7222, tcp://<host2>:7222<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:135)<br>
    =============================================
    Below are the basic JMS configuration:
    1. QueueConnectionFactory
    2. com.tibco.tibjms.naming.TibjmsInitialContextFactory
    We are on PI 7.0 and working with both Sender and Receiver JMS adapters.
    Looking for your help.
    Regards,
    Rahul

    HI,
    Please reply me for this question, or to the other one JNDI not able to connect . Both aer one and the other are same.
    --Khaleel                                                                                                                                                                                                                                                                                                                                                                                   

  • JMS Adapter not picking file in PI7.0

    Hello,
    I am working jms to jms scenario on PI7.0 Service Pack13. file is not able to pick up sendar JMS Channel. I am using WebSphereMQ Transport Protocol. JMS drivers are installed. ports and protocals are correct.
    I checked all parameters of JMS Adapter. no mistake in parameters. What is the problem. Please suggest as soon as possible.
    Thanks
    venkat

    Hi San ,
    Please checke the status of JMS communication channel. In Runtime work bench , U will get the adapter monitoring there if any activity happens it shows the event details .
    I hope picking the file is initial event so you can get some idea with those event log for Communication channel .
    Cheers,
    Reddy

  • PI unable to connect via JMS adapter to Weblogic

    Hello All,
       We have implemented JMS adapter on PI 7.11 for the first time in our landscape which connects to Weblogic server. When i test my scenario i get this Error on JMS Communication Channel. Could some one help me out .. where things are going wrong?
    Am using Transport protocol as : Access JMS Provider with JNDI
    CASE 1 :
    284272 A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with
    environment: {java.naming.provider.url=t3s://usdatlpc64m----
    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427250 having object id: 035dd91446303f17bf0e7ad9a4dbd564: RuntimeException: Exception occurred while reading the license file.<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...
    CASE2:
    A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=----
    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427251 having object id: 035dd91446303f17bf0e7ad9a4dbd564: javax.naming.NamingException: String index out of range: -1<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...

    Hi ,
    Were you able to resolve the issue?
    We are facing similar issue when trying to integrate (SOAP over JMS) with WebSphere 7.x server to read JMS messages. We are using SAP PI 7.1 version and after providing the JNDI connection factory as "com.ibm.websphere.naming.WsnInitialContextFactory".....the error returned is :
    ======
    Channel error occurred. Detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=iiop://10.60.5.115:2809, java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory, java.naming.security.principal=admin, java.naming.security.credentials=admin}for profile: ConnectionProfile of channel: JMSSender_MESon node: 8649950 having object id: a8c808c859f33b40a41d0ced2088fb18: javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...
    =====
    Thanks in Advance
    -Naveen

  • JMS Adapter (for DI) does not allow passing username and password to JMS connection

    Post Author: PLed76
    CA Forum: Data Integration
    JMS Adapter (for DI) does not allow passing username and password to JMS connection. It has those fields only for MSMQ. Our Production environment does not allow us to connect to JMS (we use Tibco EMS) anonymously, so it prevents us from use of Data Integrator. Is there any way to pass those params, or obtain the correct version of JMS Adapter, or obtain source codes of the JMS Adapter so we can correct them ourselves (we can send you the corrected sources back) ? Thanks in advance for any help. (PL)ed76 Renaissance Capital

    Bump - Were having the same issue.
    Has anyone found a way to connect to Tibco with a user/pwd?
    Version 14.0.297.

  • Release the connection in JMS Adapter

    Hi,
    I’m sending the message to JMS queue (queue is running in weblogic server) using JMS Adapter in BPEL. My question is how to release the weblogic connection once the message produced to queue. It is happen automatically or we have to release the connection explicitly. If it explicit handle means how to do it?
    It would very helpful for me if you send any reference doc or url about this.
    Thanks in Advance.
    Thanks
    Chandramohan

    The JMS adapater of SOA will handle this for you. You do not have to do anything with closing connections.
    Marc

  • JMS adapter error in MQSeries connection

    Dear All,
    i am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
    Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
         at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
         at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
    com.ibm.mq.MQException:  Message catalog not found
         at com.ibm.mq.MQManagedConnectionJ11.&lt;init&gt;(MQManagedConnectionJ11.java:171)
         at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
    i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
    i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
    So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
    Thanks and Regards,
    Rajeev Gupta
    Edited by: RAJEEV GUPTA on Jan 29, 2008 2:32 PM
    Edited by: RAJEEV GUPTA on Jan 29, 2008 2:39 PM

    Hi,
    Check this as well [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fjm35210_.htm]
    Regards,
    Venkata S Pagolu

Maybe you are looking for