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 :-)
We appear to be having the same problem.
We used to work with SoapUI 4.6.4 and recently migrated to ReadyAPI 1.3.1 (both the 64 bit version).
In SoapUI everything workes fine, but when using ReadyAPI, error JMSFMQ6312 is showing up when executing the same step.
I've attached the logging for both SoapUI and ReadyAPI. Both give the same errors at the same point, but as you can see, the JMSFMQ6312 error is only showing up when using ReadyAPI.
johand is it possible for you to try the 1.2.1 as i suggested in my post above?
It's relevant to know to track down if virt-refactoring between 1.2.1 - 1.3.1 caused this.
@OstbergM I already tried that, but unfortunately that didn't resolve the problem.
Hello,
I've dug into the issue at hand somewhat, and from the exception its pretty clear that the client(HermesJMS) is unable to find the native library mqjbnd64.dll that probably is in your WMQ installation.
You could either try to add the dependency directly to the java.library.path in ready-api.bat or
you could try to adding it to the hermesJMS/lib folder.
I'm not entirely sure the second option will work, but might aswell try it first since its much easier than appending the java.library.path-property.
If you go with java.library.path-option you need to open up ready-api.bat in your Ready Installation and modify the following line.
set JAVA_OPTS=%JAVA_OPTS% -Djava.library.path="%READY_API_HOME%\"
to
set JAVA_OPTS=%JAVA_OPTS% -Djava.library.path="%READY_API_HOME%\:C:\path\to\your\WMQ\installation\lib64""
After that has been done, please make sure you also start Ready by running the bat-file.
Have a go at it and see if that works. Otherwise, please share your Help > System Properties and any other errors you might encounter in the logs.
