Contributions
Re: Hermes Configuration Failure in Ready API 1.3.1
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.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.3KViews0likes0CommentsRe: Hermes Configuration Failure in Ready API 1.3.1
Rao - Right,SYSINT_BE is set up with server name, user name and password, and queues could befound underneath it. SoapUI 5.0.0 was able to recognize it. Error: 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!9 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.4KViews0likes2CommentsHermes Configuration Failure in Ready API 1.3.1
Hello, Afterupgrading 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 wherehermes-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? 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 Thanks in advance.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.4KViews0likes6Comments