JMS adapter fails to open IBM WebSphere MQ Manager V6 Remote Queue

Hello,
We are trying to connect to a Remote Queue with the SAP PI 7.0 SP9 JMS adapter to IBM WebSphere MQ V6 on Linux SLES9 x86_64.
We did deployed the JMS-adapter with the V6 native libaries on SAP PI.
In the Communication Channel we use the Adapter Type = JMS, Sender, Transport Protocol = WebSphereMQ(non-JMS).
The MQ Queue Manager is on the same server as SAP PI so we use localhost, Server Port, Queue Manager Name, Channel Name and JMS Queue Name
The <sid>adm user is a member of the mqm group.
When I check the RWB I see this fault message:
Error during channel initialization; exception trace: javax.jms.JMSException: <b>MQJMS2008: failed to open MQ Queue</b> at ...
and also
com.ibm.mq.MQException: <b>MQJE001: Completion Code 2, Reason 2045</b>
When we lookup the reason 2045 we get this explaination on MQ:
MQRC_OPTION_NOT_VALID_FOR_TYPE
We also have a type = Receiver Communication Channel on the same MQ Queue Manager that one is working fine.
Please advise!
Best regards,
Mike Laanen

Mike,
check whether the Queues are created and activated if it done. then check whether you have authorization for those queues.
Regards
Sreeram.G.Reddy

Similar Messages

Flow is not going to catch block when JMS adapter fails

In a BPEL composite, we have a JMS adapter to write a message into JMS Queue.
In this error scenario, JMS is down & so JMS adapter fails with the below error. But control is not going to the catch block where we have some logic to construct a error response. Why?
Global retry rollback fault thrown.
The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new JTA transaction upon catching this fault.
This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.
There is no action recommended.
BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: ERRJMS_PROVIDER_ERR.
ERRJMS_PROVIDER_ERR.
Unable to produce message due to JMS provider internal error.
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.

Hi,
This is similar to JTA issue from below post.
CatchAll block not catching JTA timeout with XA datasource. Try the suggestion given by Riaan and see if it helps.
Regards,
Sai

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

If you want to use JMS with AQ as datastore then there is some configuration you need to do to enable this. This is outside SOA Suite per sa, e.g. no adapter required.
If you want to connect to the AQ direct then use the AQ adapter.
this blog may be of some help understand the configuration
http://biemond.blogspot.com/2008/01/oracle-jms-with-esb-and-bpel.html
cheers
James

JMS Adapter Fail - Receiver channel. Details: Receive timed out

Its an IDOC to JMS scenario. IDOC gets processed through the pipeline in XI successfully, can see the checkered flag.
However in Adapter monitoring, JMS adapter is in red.
The error text against the Communication Channel is "Receiver channel. Details: Receive timed out".
I am trying to connect to the JMS queue provided by a third party on port 1100 ( as configured in JMS adapter).My initial analysis is to check if the port is open on the third party's firewall( Need to get the response back from them yet).
However i would like to know, if there is something else that i should look into?

Following are the error messages in RWB audit log for the message sent.
Exception caught by adapter framework: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out
Error Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out.
what might be the problem?

How to send alert when receiver JMS adapter fails? Please help!

Hi experts,
   I have the following Asynchronous scenario:
   SAP R/3 -
>IDOC----->XI>JMS--->BizTalk.
   I am sending IDOC from a given SAP R/3 system to XI. XI then sends the same to BizTalk via JMS adapter. In SXMB_MONI the message is successfully processed as it shows checked flag. But if I see the JMS communication channel status in runtime workbench then there it shows error saying JMS queue user id or password not found.
How to send this JMS adapter error as alert?
I also tried configuring alert rule in runtime workbench but still it does not trigger any error.
I have also verified the alert category and everything is fine with that.
What could be the problem? How can I send an alert when an Async adapter fails?
Thanks & Regards,
Gopal

Hi! GOPAL,
Once make sure whther all the below mentioned steps are configured correctly or not ok
1: First make sure whether you are working on SAP XI or PI 7.1
           a) If XI you need to create Alerts (ALert Category) in CCMS ABAP stack in the
                    Tcode. ALRTCATDEF
           b) Open the alert category/classification definition environment (transaction ALRTCATDEF).
     ensure you are in change mode.
           c) In the group box with the alert classifications, right-click All classifications to open the
                context menu, and choose Create.
           d) Under Classification, enter a name for the classification.
           e) Under Description, enter a description of the classification.
           f) Save your entries.
           g) Then go to RWB-->Go to ALERT Configuation and ADD the RULES to your alert category gor
     which created there in the abap stack.
Note Suppose if you want those ALERTS to come to your MAIL then again go to ABAP STACK and go to Tcode. ALRTCATDEF and select your alert category press FIxed Recepients and there give your SAP XI ID's then u can see those alerts in RWB-->ALERT INBOX
Suppoe if you want those to mail then ask the basis team to link your company mail or personal mail ID to your SAP ID.
2. Supppose if you are working on PI 7.1 Server.
     Only difference is creating Alert Category...Here you can create your ALERT Classification I mean
     alert caltegory in the ESR (Enterprise Service Repository )
     Software Component >S CVersion>NameSpace-->Alert Category.
     You can configure how u configure there in abap stack such as long and short text every thing
      except Fixed Receipients you need to give that recepients there only in ABAP STACK.
      what ever ALERT CATEGORY you are creating will reflect there in the ABAP STACK
     even you can Use these alerts Category in BPM --> CONTROL STEP -->Configure here in this step
You can also reach alerts like this.
NOTE Most Important point is You can also view your mails or Alerts in the T Code:: SOST.
Regards:
Amar Srinivas ELi

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

Error in JMS Adapter while communicating with WebSphere MQ 7.5

Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.

Problem solved after removing j2ee.jar file from classpath !

User and Password for JMS-Adapter

Hi all,
when configuring JMS-Adapter e.g. for IBM MQSeries i do not find field where to specify the user and password for the MQ. We configure e.g. a receiver communication channel.
In 2.0 JMS-Adapter we can put user and password like this
JMS.QueueConnectionFactoryImpl.user=YTEST
JMS.QueueConnectionFactoryImpl.password=<!%YTEST%!>
in the property file. We can also hide the passwort with
the mechanism of password token.
How can this be done in JMS 3.0 Adpater? Is it possible?
Thanks,
Ly-Na Phu

Oh, sorry. Now i see the field for user and passwort.
Thanks,
Ly-Na Phu

Jms adapter is very slow

hi all
I've got two bpel processes deployed: one is writing message into a queue (created in 10g Oracle DB) using jms adapter, second one is supposed to read message from the queue. It seems to work very slowly, bpel part is executed fast (everything is deployed on fast linux server) but reading from a queue is a bottleneck. It takes rougly 1 second to read a single message from the queue !!!!
I tried with and without connection pooling and I get the same results.
I also tried to read from the same queue from a standalone java application: it takes 50-150ms to read one message after obtaining connection.
My configuration:
As 10.1.3.1
adapter wsdl relevant part:
<binding name="Consume_Message_binding" type="tns:Consume_Message_ptt">
<pc:inbound_binding />
<operation name="Consume_Message">
<jca:operation
ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec"
DestinationName="java:comp/resource/ASDBResource/Queues/LSP_INPUT_Q_BRIDGE"
UseMessageListener="false"
PayloadType="BytesMessage"
OpaqueSchema="true" >
</jca:operation>
</binding>
<service name="InboundJMS">
<port name="Consume_Message_pt" binding="tns:Consume_Message_binding">
<jca:address location="eis/Jms/JMSDBConnection" UIConnectionName="JMSDBConnection"
ManagedConnectionFactory="oracle.tip.adapter.jms.JmsManagedConnectionFactory"
mcf.ConnectionFactoryLocation="java:comp/resource/ASDBResource/QueueConnectionFactories/QCF"
mcf.IsTopic="false"
mcf.IsTransacted="true"
mcf.FactoryProperties=""
UIJmsProvider="OJMS" />
</port>
</service>
ASDBResource is configured in application.xml to point to a proper machine.
When I set useMessageListener to "true" I get even worse performance.
I found following text in adapters faq, maybe there is an option to change pooling interval ?
<The JMS API supports both synchronous or asynchronous communication for <message consumption. In the
<synchronous case, the consumer explicitly calls the receive() method on the <topic or queue. In the
<asynchronous case, the JMS client registers a MessageListener for the topic or <queue and the message is
<delivered by calling the listener’s onMessage() method. By default, the consumer <uses a polling method. The
<Adapter design-time is used for overriding the default behavior and can be used to <configure a message listener
<for receiving JMS messages in an asynchronous fashion.
cheers
Przemek

If speed is of essence, have you considered using the AQ adapter instead ? That should be faster when compared to the jms route, assuming you are going against Oracle AQs.

Store and Forward agent configuration in jms adapter - jdeveloper

I am created the store and forward (SAF) agent in weblogic to communicate with another weblogic server.
after creating it i tried to configure it in jms adapter wizard but i can't able see my SAF Queue there.
so now how can i give payload to my SAF queue for testing it.
Please provide any suggestions, i will provide with the points.
Thanks,
Ajay Athuluri

So I don't know much of the details of AIA, and next to nothing of the pre-built integrations, so can't help you much there. However are you sure you've got all the requisite SAF configuration right? The JMS and SAF component hierarchies are a real rats' nest of trouble. This is a setup I've found to work:
* SAF Agent, targeted to a managed server; needs to use the default filestore (ie when configuring it you don't specify one)
* JMS Module containing:
     * SAF Remote Context, pointing at your remote WLS instance
     * JMS SubDeployment, targeted to the SAF Agent
     * Connection Factory, targeted at the managed server
     * SAF Imported Destination, targeted at the SubDeployment
     * Queue in the Imported Destination, with WLS and JNDI names set up so they're different in the sending domain and receiving domain
The pre-built integrations will (probably) have the JNDI names you need to configure in the documentation.
HTH!
Paddy

ITunes window fails to open.

After upgrading to iTunes 10, the iTunes window fails to open. In task manager, the iTunes process runs, and occasionally the "Checking iTunes library" dialogue will pop up, but the window itself does not open. I have already tried most of the suggestions on the Apple help page [http://support.apple.com/kb/TS1421]. The issue is system-wide and I have tried the following:
* Removing iTunes Configuration Files
* Fix digital signing of Windows drivers
* Check the iTunes and QuickTime installations
However, the problem continues. It is not a problem with a virus on my PC, nor with a conflicting program. I'm at a loss as to what is causing this.
PC meets all the required specs to run iTunes, except graphics card drivers are out-of-date. There is nothing I can do about this short of purchasing a new graphics card, however previous versions of iTunes have run fine.
Can give more details if required, hoping for a fix.
Thanks

Try removing the Genius database.
In the "Finder" go to the /username/Music/iTunes/ directory and delete the "iTunes Library Genius.itdb" file. This may allow the program to launch again. This file will be recreated upon first use of the "Genius" feature.

JMS Receiver Adapter - com.ibm.websphere.naming.WsnInitialContextFactory

Hello experts,
I am trying to configure JMS Adapter to Access Websphere Application Server via JNDI. The configuration is as follow:
Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Connection Factory: jms/messageQueueCF
Server URL: iiop://ammtnode.iubs.intra:2809/
Queue Name: jms/EXT_INPUT_QUEUE
I deployed all required jar files but Iu2019m still unable to connect to WAS because adapter cannot initialize ORB:
javax.naming.NamingException: Failed to initialize the ORB
I wrote a small java class to check where the problem was:
============================================================================
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://ammtnode.iubs.intra:2809/");
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
Context jndiContext = null;
try {
jndiContext = new InitialContext(env);
ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.lookup("jms/messageQueueCF");
Connection qConn = connectionFactory.createConnection();
Session qSession = qConn.createSession(false,Session.AUTO_ACKNOWLEDGE);
Queue q = (Queue) jndiContext.lookup("jms/EXT_INPUT_QUEUE");
MessageProducer producer = qSession.createProducer(q);
TextMessage message = qSession.createTextMessage();
message.setText(text);
producer.send(message);
producer.close();
qSession.close();
qConn.close();
} catch (Exception e) {
     e.printStackTrace();
============================================================================
I got the same error until I wrote this line:
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
And everything worked fine. Now I want to do the same in my JMS Receiver adapter but I donu2019t know how to introduce this line in the Initial Context Environment. I tried as JMS additional parameters and additional properties as well. However, nothing worked. Does anybody know what Iu2019m doing wrong?
Thank you in advance!

Here I post the entire error:
0#0#Warning##Java###Catching #1#com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection fact
oryjms/messageQueueCF, for profile: ConnectionProfile of channel: CC_I002_AMM_JmsReceiveron node: 5949650 having object id: 0
360697bc61b3666aba07a2708ca095a: javax.naming.NamingException: Failed to initialize the ORB
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:134)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
        at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
        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:152)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class
com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:libra
ry:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
        at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
        at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
        at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
        ... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
        at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
        at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
        at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
        ... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
        at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
        at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
        at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
        ... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
        at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
        at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
        at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
        ... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
        at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
        at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
        at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
        at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
        at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
        at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
        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:152)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
        at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
        at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
        at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
        at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
        at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
        ... 19 more

Problem with Send using JMS Adapter with Websphere MQ

Hi,
We have two scenarios using JMS Adapter with MQ:
1. File->PI->MQ
This works fine and drop the file in MQ correctly.
2. MQ->PI->File
This gives an error reading from the queue: (see highlighted in the log below). It correctly connects to the queue name. But it fails with the message "Could not begin a AF transaction".
Our PI version is 7.0 SP 13
Websphere MQ Version 6.0.
Any idea what could be wrong?
Cluster Node Administration Information Availability Times
Cluster Node Details for Channel CC_JMS_MQ_Sender
Short Log
In the Last 4 Hours Server 0 15_92786
_Sucessfully connected to destination 'queue:///MMPP.PLM.FGH41? CCSID=37&targetClient=1'_
Line 1 / 1
Processing Details for Cluster Node Server 0 15_92786
Type
Time Stamp
Message ID
Explanation
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d Error while processing message '2e6206f0-7925-11dd-bc02-0003bae50b4d'; _detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ..._
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d XI message ID corresponding to JMS message with ID 'ID:414d512071736431202020202020202047d9462024028b02' will be created as a new GUID with value '2e6206f0-7925-11dd-bc02-0003bae50b4d'
Amith Dharmasiri

Checked the drivers installed in :
/usr/sap/<SID>/DVEBMGS<SYSNO>
/j2ee/cluster/server0/bin/ext/com.sap
.aii.af.jmsproviderlib
They are available and properly added to aii_af_jmsproviderlib.sda.
The drivers are:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
These were installed per OSS note 747601.
Any other suggestions, why retrieving from MQ doesn't work?

Problem in JMS-Adapter with CharacterSet Websphere MQ

Hi,
we have the following scenario:
JMS -> PI -> File
We have a local Websphere MQ Queue Manager and the follwoing configuration in our sender adapter:
Transport-Protocol: WebSphere MQ (non JMS)
Message-Protocol: JMS 1.x
ConnectionFactory: com.ibm.mq.jms.MQQueueConnectionFactory
Java-class Queue: com.ibm.mq.jms.MQQueue
CCSID: 819
Transport: TCP/IP
JMS-conform: WebSphere MQ (non JMS)
In the local queue manager the messages (XML-Messages with header <?xml version="1.0" encoding="ISO-8859-1"?>) have characterSet 819 (ISO-8859-1). That's correct. You can open the files with XMLSpy and it works.
When we receive the messages by our JMS Sender Adapter all the character seems to be in UTF-8 and I don't know why. All the special characters are wrong cause the header of the XML-message shows ISO-8859-1 but all the signs are decoded in UTF-8.
In the other direction (JMS Receiver adapter, File -> PI - JMS) we have the same problem.
We create a ISO-8859-1 message in mapping (and it is really ISO-8859-1) and send it via JMS Receiver Adapter to the local message queue. But there the message arrives in UTF-8 encoding. I don't understand this.
Does anybody know what could be the cause for this?
Does the JMS adapter convert the messages from ISO-8859-1 into UTF-8?
Are there any parameters we have to set?
I hope anybody has an idea what's wrong.
Regards
Thorsten
Edited by: Thorsten Hautz on Oct 12, 2010 5:42 PM

Hi,
thanks a lot for your replies.
our driver settings are correct (as I can see).
I removed value 819 from CCSID, but we have the same effect.
The messages in the local queue manager are TextMessages in XML.
Does anybody know, if we need the standard modules (ConvertJMSMessageToBinary and ConvertBinaryToXMBMessage) in this case?
Is it possible to set the CCSID for the message payload anywhere in the configuration?
The CCSID in the Source tab doesn't have any influence to the encoding of the payload message, only to the header data.
Regards
Thorsten

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 fails to open IBM WebSphere MQ Manager V6 Remote Queue

Similar Messages

Maybe you are looking for