Problem with Send using JMS Adapter with Websphere MQ

[Former Member]

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

[Former Member]

Hi Amit,

Can you please explain exactly what you did to solve this problem? We are having the same problem in our production environment but this is happening with only 1 communication channel where as we have about 30 other communication channels reading from the MQ-queue without any problems.

Kind regards,

Joe

[Former Member]

Hi,

We have found the solution to this problem.

We were at SAP-XIAF and SAP-XIAFC at base SP level 13.

This base level is reported to have errors confirmed by SAP.

There are downloadable patches available in SAP Service Market Place for these two to fix those erros.

Once we applied the patches the problem was fixed.

Amith

[Former Member]

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?

[Former Member]

Drivers are correctly installed. I will double check this with our Basis.

Notice that writing to MQ works fine. File->PI->MQ

Reading from MQ is the problem.

Amith

[Former Member]

That is how it is setup already.

Amith

[Former Member]

Hi Amit

Please check the installation of the drivers by checking in the /usr directory as mentioned in the "How to guide" for installing external drivers.

This is the reason u are getting this error

This should hopefully sove your problem.

Regards,

Nipun

[Former Member]

Hi Nipun,

Thank you for quick reply.

Yes. I tried restarting the channel several times. But it gave the same error each time.

Let me know any particular parameter(s) that you would like to see in the settings.

Regards,

Amith

[Former Member]

Amit,

Please check this, I hope this must help.

Make sure that Correlation settings have entries as

Set XI Message ID (MessageID) To: GUID (Recommended Value)

Link: [http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm]

Let me know if you still finds any problem.

[Former Member]

Hi Amit,

This may be a temporary problem in connection, I beleive you should try restarting the communication channel.

If restarting doesn't work, then we need to check what communication settings are having entries.

Regards,

Nipun