We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Hi zijst005
Thanks for reporting your problem. We found out that it is actually a bug, related to Ready! API - Hermes interaction. While we are working on it, you could use a workaround: copy the following jars from ReadyAPI-1.4.0/hermesJMS/lib to ReadyAPI-1.4.0/lib:
Also, make sure you set connection parameters in Hermes both for plugin (serverUrl, username, password) and connection factory (serverUrl, userName, userPassword) - the values should be the same.
Please, write back how that will work out.
Hi nmrao,
First of all thanks for all your support/time.
I have taken the hermes-config-sample.xml and with some minor adjustments i updated the the path to the jar files and adjusted the serverUrl.
however the result remained the same, a colleage of mine is facing the same issue.. and currently Smartbear has acknowledged/reproduced the issue. they created a case for it, so hopefully they are diving into it :)
Personally i don't think it is related to the hermes-config.xml. The reason i don't think its related to that, is because HermesJMS which is using the Same config is able to Contact the server and is able to discover the queues.
So from an configuration point of view i would expect the Config file along with the Providers (jar files) to be correct.
Hi zijst005
Thanks for reporting your problem. We found out that it is actually a bug, related to Ready! API - Hermes interaction. While we are working on it, you could use a workaround: copy the following jars from ReadyAPI-1.4.0/hermesJMS/lib to ReadyAPI-1.4.0/lib:
Also, make sure you set connection parameters in Hermes both for plugin (serverUrl, username, password) and connection factory (serverUrl, userName, userPassword) - the values should be the same.
Please, write back how that will work out.
Hi AntonE,
This definilty fixed the issue.
Thanks for providing the workaround!