Forum Discussion

zijst005's avatar
zijst005
Occasional Contributor
9 years ago
Solved

Ready! API 1.4 Always refering to tcp://localhost:7222 eventough HermesJMS is correctly configured

Hi all,   I hope there is someone here who can help me out with the following scenario:   I installed Ready API 1.4  and I have Created an HermesJMS Connection to a remote EMS server From within...
  • AntonE's avatar
    AntonE
    9 years ago

    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:

    • asm-2.1.jar
    • asm-commons-2.1.jar
    • asm-util-2.1.jar
    • cglib-2.2_beta1.jar

    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.

nmrao's avatar
nmrao
Champion Level 3
Can hermes-config.xml file be attached, just in case to see every thing is alright or to isolate the issue?
  • nmrao's avatar
    nmrao
    Champion Level 3
    9 years ago

    Looks there are multiple sessions configured.

     

    Here attaching the sample configuration file, and hope you will be able to find the dependencies that you see in the attached configuration file. It also uses password, so you see that there.

    • zijst005's avatar
      zijst005
      Occasional Contributor
      9 years ago

      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.

       

      • AntonE's avatar
        AntonE
        SmartBear Alumni (Retired)
        9 years ago

        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:

        • asm-2.1.jar
        • asm-commons-2.1.jar
        • asm-util-2.1.jar
        • cglib-2.2_beta1.jar

        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.