Well, I posted a case and got a workaround: replace commons-beanutils-1.8.3.jar in {ReadyAPI install}/lib with commons-beanutils-1.7.0.jar from {SoapUI Pro install}/lib.
Seems to do the trick :-)
Yes, I was also triggered by that message (the missing mqjbnd64.dll). Problem is, we don't have a full WMQ installation. Our C:\Program Files (x86)\IBM\WebSphere MQ directory, where the file should be is empty.
Another thing to consider: the error occurs even when using the same HermesJMS client and hermes-config.xml file. Somehow SoapUI doesn't have any problem and doesn't throw the missing dll-file error, but ReadyAPI does.
One extra thing to add is, we've added the following jar-files to HermesJMS in the providers-tab and use those to set up our connection:
-commonservices-7.5.0.2.jar
-connector.jar
-dhbcore-7.5.0.2.jar
-headers-7.5.0.2.jar
-jmqi-7.5.0.2.jar
-mq-7.5.0.2.jar
-mqjms-7.5.0.2.jar
-pcf-7.5.0.2.jar
I've also attached both system properties and included the hermes configuration file.
I tried setting the transportType to null earliers. Still the same result.
I also installed the IBM MQ Websphere Client to see if that helps. Unfortunately no help. I did find that there is no mqjbnd.dll of mqjbnd64.dll present in it, even when installing the client. Suposedly, the dll is only present when you install MQ Websphere Server.
The only thing I can think of is that ReadyAPI ignores the transportType set in the hermes-config.xml and always tries to use Binding mode instead of Client mode to connect to JMS. That is why it tries to find the dll-file. But this dll-file is only needed when using Binding mode.
Yes, i'm pretty sure that's what is going on too. Confusing as it may seem as the properties should be set to exactly as they are defined in the hermes-config.xml file.
I'll try to debug some using your hermes-config.xml and see where the property gets set to Binding-mode. I'll try to have that done during the day, but i can't make any promises that it'll unravel anything valuable.
