Forum Discussion

zijst005's avatar
zijst005
Occasional Contributor
10 years ago

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
    10 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.

zijst005's avatar
zijst005
Occasional Contributor

don't know if this helps you but here is an extract taken from the SoapUI debug window:

 

This happens when i sent the message:

 

14:07:20,112 WARN  [HermesJmsRequestTransport] Invalid timeout extracted (not a
number): null

 

 
14:07:23,407 ERROR [SoapUI] An error occurred [Failed to connect to the server a
t tcp://localhost:7222], see error log for details
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
        at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:831
)
        at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:922)
        at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1299)

        at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4155)
        at com.tibco.tibjms.TibjmsTopicConnection.<init>(TibjmsTopicConnection.j
ava:36)
        at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:191)
        at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:2
53)
        at com.tibco.tibjms.TibjmsConnectionFactory.createConnection(TibjmsConne
ctionFactory.java:36)
        at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolde
r.createConnection(JMSConnectionHolder.java:87)
        at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSe
ndReceiveTransport.execute(HermesJmsRequestSendReceiveTransport.java:39)
        at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTr
ansport.sendRequest(HermesJmsRequestTransport.java:100)
        at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
14:07:23,436 WARN  [HermesJmsRequestTransport] Error Response
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
        at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolde
r.createConnection(JMSConnectionHolder.java:102)
        at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSe
ndReceiveTransport.execute(HermesJmsRequestSendReceiveTransport.java:39)
        at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTr
ansport.sendRequest(HermesJmsRequestTransport.java:100)
        at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
nmrao's avatar
nmrao
Champion Level 3
10 years ago
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
      10 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
        10 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.