Hermes Configuration Failure in Ready API 1.3.1

Question

Hello,&nbsp;After&nbsp;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&nbsp;hermes-config.xml is placed and it doesn't seem like a problem. I have searched online and it seems like some other people had the same issue but nobody got it resolved:mansad:. Any suggestions?&nbsp;Mon Jul 20 17:06:25 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&nbsp;Thanks in advance.

nmrao · Answer

May be you just try invoking hermes and see if you are able to connect to the jms using the same configuration file.

bluefire · Answer

Rao -&nbsp;&nbsp;Yes, I am able to invoke Hermes from Tools -&gt; HermesJMS. All TIBCO&nbsp;EMS sessions are there.

nmrao · Answer

Ok, so do you see SYSINT_BE there? And what soap logs says and when you see the issue exactly?

bluefire · Answer

Rao -&nbsp;&nbsp;Right,&nbsp;SYSINT_BE is set up with server name, user name and password, and queues could be&nbsp;found underneath it. SoapUI 5.0.0 was able to recognize it.&nbsp;Error:&nbsp;&nbsp;Complete error log:&nbsp;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 sessionjavax.naming.NameNotFoundException: binding SYSINT_BE does not existat 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&nbsp;&nbsp;Appreciate your willingness to help!

nmrao · Answer

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.

Forum Discussion

Hermes Configuration Failure in Ready API 1.3.1

6 Replies

Related Content

Hermes configuration issue

Hermes Configuration Issue in Ready API

MSTest Configuration

Using sendmail for test failure alerts

DNS server failure

Recent Discussions

Parameterising JDBC Connection Settings..Can you do it?

How to remove (not clear) test case properties from SaveScript

Remove Properties of TestCase from Groovy.

MyFirstPlugin - button Project menu in Ready Api

Integrate ReadyApi with Devops Release pipelines