Forum Discussion

bluefire's avatar
bluefire
New Contributor
9 years ago

Hermes Configuration Failure in Ready API 1.3.1

Hello,   After upgrading my SoapUI 5.0.0 to Ready API 1.3.1, I found out that JMS test steps that used to work do not now. Below is the error message. C:\.heremes is where hermes-config.xml is plac...
bluefire's avatar
bluefire
New Contributor

Rao - 

 

Yes, I am able to invoke Hermes from Tools -> HermesJMS. All TIBCO EMS sessions are there.

nmrao's avatar
nmrao
Champion Level 3
9 years ago
Ok, so do you see SYSINT_BE there? And what soap logs says and when you see the issue exactly?
  • bluefire's avatar
    bluefire
    New Contributor
    9 years ago

    Rao - 

     

    Right, SYSINT_BE is set up with server name, user name and password, and queues could be found underneath it. SoapUI 5.0.0 was able to recognize it.

     

    Error:

     

    JMS error dialog.png

     

    Complete error log:

     

    JMS Endpoint String does not contain a parameter at index 2, parameters: [SYSINT_BE, queue_SYSINT.PU.CO.CUSTOMSREQ.PROCESSCUSTOMSRESPONSE.Q.V1]
    JMS Endpoint String does not contain a parameter at index 2, parameters: [SYSINT_BE, queue_SYSINT.PU.CO.CUSTOMSREQ.PROCESSCUSTOMSRESPONSE.Q.V1]
    Thu Jul 23 11:05:47 PDT 2015:ERROR:Error when trying to find JMS session
    javax.naming.NameNotFoundException: binding SYSINT_BE does not exist
    at hermes.impl.jms.ContextImpl.assertBindingExist(ContextImpl.java:336)
    at hermes.impl.jms.ContextImpl.lookup(ContextImpl.java:250)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils.getHermes(HermesUtils.java:185)
    at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.getHermes(HermesJmsRequestTransport.java:200)
    at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.init(HermesJmsRequestTransport.java:102)
    at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSendTransport.execute(HermesJmsRequestSendTransport.java:35)
    at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.sendRequest(HermesJmsRequestTransport.java:97)
    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)
    Thu Jul 23 11:05:47 PDT 2015:ERROR:An error occurred [Session name 'SYSINT_BE' does not exist in Hermes configuration or path to Hermes config ( C:\.hermes )is not valid!], see error log for details

     

     

    Appreciate your willingness to help!

    • nmrao's avatar
      nmrao
      Champion Level 3
      9 years ago
      Requesting for couple more information, bear with me.
      1. Are you trying soapui for SOAP over JMS?
      2. What is the endpoint string that you are using?
      3. attach hermes-config.xml for just have a look.
      • bluefire's avatar
        bluefire
        New Contributor
        9 years ago

        Rao - 

         

        1. The message being sent is a simple XML text message.

         

        2. jms://SYSINT_BE::queue_SYSINT.PU.CO.CUSTOMSREQ.PROCESSCUSTOMSRESPONSE.Q.V1

         

        3. I attached a copy of it with password manually removed.