Loadrunner JMS Scripting

Question

I have created one LoadRunner JMS script to send a XML message to IBM Websphere Queue, the message reached the Queue and it throws the following error while it processed by IBM BPM consumers

Error : MQ w exception thrown in header data binding

RFH2Databindings encountered a bad value at com.ibm.ws.sca.mq.data.impl.RFH2databindings.read

Please help me in understanding why this error happened and is there any wrokaround i can do in my scripts

Answer 1

It sounds as though the client on the scripting machine is a back-level. The RFH2 headers are no longer used with modern WebSphere MQ versions and have been replaced by Message Properties. The reason the new .bindings file will have worked would be either that a) it defaults to a setting that does not generate the offending property value; b) the client is capable of generating message properties and the new .bindings file does not enable compatibility; c) the client on the scripting machine has a bug.

If the scripting machine has a full client install, you can use the dspmqver command to see which version it is. If it is not at least WMQ V7.1, it really, desperately, needs an upgrade and preferably to v7.5. The newest client code (with Fix Packs applied) is at:

• WMQ V7.1 Client is SupportPacMQC71.
• WMQ V7.5 Client is SupportPacMQC75. (Strongly preferred.)
• The stand-alone WMQ Explorer is SupportPac MS0T.
• The indispensable utilities plugin for WMQ Explorer is SupportPac MS0P.

When installing the WMQ client, install all of the features. If you just grab the jar files the installation is not supported by IBM and you do not get any of the diagnostic utilities. However, if you feel you really must grab jar files, install the client to a VM or other throw-away machine and grab the jars you need. Since this is not a supported configuration, there is no documentation about the minimum set of jar files to grab so just get the entire directory.