Hermes JMS not working properly with Ready API 1.5.0

TanyaYatskovska
SmartBear Alumni (Retired)
10 years ago
Hi mileppaa,

Thanks for submitting this issue to our Ready! API Customer Care team. I hope our developers will be able to fix it as soon as possible.

Champion Level 3

10 years ago

Ok. In general, one should consider migrating to new version if there such a desperate need. Any way it is better to have check criteria before taking a new version.
Have you also added above comment regarding switching tool while raising the issue with support?

przemekch

Occasional Contributor

10 years ago

I'm using the latest snapshot with the maven build run from Jenkins

http://smartbearsoftware.com/repository/maven2/com/smartbear/ready-api-maven-plugin/1.5.0-m-SNAPSHOT/ready-api-maven-plugin-1.5.0-m-SNAPSHOT.pom

            <plugin>
               <groupId>com.smartbear</groupId>
               <artifactId>ready-api-maven-plugin</artifactId>
               <version>1.5.0-m-SNAPSHOT</version>
               <executions>
                   <execution>
                       <id>someTest</id>
                       <goals>
                           <goal>test</goal>
                       </goals>
                       <phase>test</phase>
                       <configuration>
                           <projectFile>${basedir}/someTest-soapui-project.xml</projectFile>
              <settingsFile>c:\Dev\soap-ui-settings\soapui-settings.xml</settingsFile>
                           <outputFolder>${project.build.directory}/surefire-reports</outputFolder>
                           <junitReport>true</junitReport>
                           <printReport>false</printReport>
                           <environment>${env}</environment>
                       </configuration>
                   </execution>
               </executions>

               <dependencies>

                     <dependency>
                       <groupId>org.reflections</groupId>
                       <artifactId>reflections</artifactId>
                       <version>0.9.9-RC1</version>
                   </dependency>
                   <dependency>
                       <groupId>org.apache.poi</groupId>
                       <artifactId>poi-ooxml</artifactId>
                       <version>3.10-FINAL</version>
                   </dependency>
                   <dependency>
                       <groupId>org.apache.xmlbeans</groupId>
                       <artifactId>xmlbeans</artifactId>
                       <version>2.4.0</version>
                   </dependency>
               </dependencies>
           </plugin>

13:45:58,611 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-imq.jar for hermes.ext.imq.ImqAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-aq.jar for hermes.ext.oracle.aq.OracleAQAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-ems.jar for hermes.ext.ems.TibcoEMSAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-webspheremq.jar for hermes.ext.mq.MQSeriesAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-jbossmq.jar for hermes.ext.jbossmq.JBossMQAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-arjuna.jar for hermes.ext.arjuna.ArjunaMSAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-weblogic.jar for hermes.ext.weblogic.WebLogicJMSAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-joram.jar for hermes.ext.joram.JoramAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-wme.jar for hermes.ext.wme.WMEAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-openjms.jar for hermes.ext.openjms.OpenJMSAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-fiorano.jar for hermes.ext.fiorano.FioranoAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-sonicmq.jar for hermes.ext.sonicmq.SonicMQAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-sapjms.jar for hermes.ext.sap.SAPJMSAdminFactory
13:45:58,612 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-activemq.jar for hermes.ext.activemq.ActiveMQAdminFactory
13:45:58,613 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-seebeyond.jar for hermes.ext.seebeyond.ican.SeeBeyondICANAdminFactory
13:45:58,613 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-seebeyond.jar for hermes.ext.seebeyond.jcaps.SeeBeyondJCAPSAdminFactory
13:45:58,613 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-sapjms.jar for hermes.ext.sap.SAPJMSAdminFactory

[ERROR] Error when trying to find JMS sessionjavax.naming.NamingException: No message, linked exception is : null
	at hermes.HermesContext.load(HermesContext.java:88)
	at hermes.HermesInitialContextFactory.getInitialContext(HermesInitialContextFactory.java:95)
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
	at javax.naming.InitialContext.init(InitialContext.java:244)
	at javax.naming.InitialContext.<init>(InitialContext.java:216)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils.getHermes(HermesUtils.java:118)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils.hermesContext(HermesUtils.java:91)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils.getHermes(HermesUtils.java:233)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils$getHermes.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133)
	at Script1.run(Script1.groovy:27)
	at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:92)
	at com.eviware.soapui.support.scripting.groovy.SoapUIProGroovyScriptEngineFactory$SoapUIProGroovyScriptEngine.run(SoapUIProGroovyScriptEngineFactory.java:76)
	at com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep.run(WsdlGroovyScriptTestStep.java:155)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:234)
	at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:130)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
[ERROR] Error when trying to find JMS sessionjavax.naming.NamingException: No message, linked exception is : null
	at hermes.HermesContext.load(HermesContext.java:88)
	at hermes.HermesInitialContextFactory.getInitialContext(HermesInitialContextFactory.java:95)
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
	at javax.naming.InitialContext.init(InitialContext.java:244)
	at javax.naming.InitialContext.<init>(InitialContext.java:216)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils.getHermes(HermesUtils.java:118)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils.hermesContext(HermesUtils.java:91)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils.getHermes(HermesUtils.java:233)
	at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils$getHermes.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133)
	at Script1.run(Script1.groovy:30)
	at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:92)
	at com.eviware.soapui.support.scripting.groovy.SoapUIProGroovyScriptEngineFactory$SoapUIProGroovyScriptEngine.run(SoapUIProGroovyScriptEngineFactory.java:76)
	at com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep.run(WsdlGroovyScriptTestStep.java:155)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:234)
	at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1)
	at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:130)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
13:46:04,074 ERROR [SoapUI] An error occurred [Session name 'dev14-jms1' does not exist in Hermes configuration or path to Hermes config ( C:\.hermes )is not valid!], see error log for details
13:46:04,074 ERROR [SoapUI] An error occurred [Session name 'dev14-jms1' does not exist in Hermes configuration or path to Hermes config ( C:\.hermes )is not valid!], see error log for details
13:46:04,077 ERROR [errorlog] javax.naming.NamingException: Session name 'dev14-jms1' does not exist in Hermes configuration or path to Hermes config ( C:\.hermes )is not valid!
javax.naming.NamingException: Session name 'dev14-jms1' does not exist in Hermes configuration or path to Hermes config ( C:\.hermes )is not valid!

So I wen't into the GUI version and the same issue occures...

hermes config can't be loaded by soap ui anymore

1.5.0 version is really buggy

nmrao
Champion Level 3
10 years ago
Couple of things from the above post:
1. It is not able to find the valid hermes-config.xml in the provided location 'C:\.hermes', please check.

2. I do not know about maven. I believe there can be way to set the heremes configuration location if you are not using the default location. Otherwise, you may try with default location.

3. Not sure why it is not able to locate the library files (jars). Do you want to try with absolute location.

For now these are the pointers to try.

Forum Discussion

Hermes JMS not working properly with Ready API 1.5.0

Related Content

Device Keys not working properly

List box selection is not working properly

SoapUI on Windows 10 screens not working properly

Hermes configuration issue

Trouble Getting Conditional Goto to Work Properly

Recent Discussions

Sudh budh bar hshs the day of

Assert Step Not Executing All Assertions

Include external files (XML) for JDBC connection

Accessing database connection string from groovy test step

JDBC database connection pooling