When testing jms, ready api is having error while it works fine on soapui

Hello aremSOAP, 

Have you made sure that you are using the same hermesJMS installation in Ready and SoapUI? 

They both come bundled with it, so please make sure that you haven't got two separate hermesJMS installations in both tools, in case you put any special jars in your lib-folder.

Reason i'm asking is because it looks like Ready! API is unable to do one of the following things based on this error: 

• Get the ConnectionFactory defined in HermesJMS
• Create the connection with or without the correct credentials from the ConnectionFactory
• Start the connection

So my best bet is that something is acting up with Ready's connection to hermes. 

If that looks allright then please check to see if there's any difference running these two versions of Ready. 

Ready! API 1.2.1 VS Ready! API 1.3.0 

Because if something changed for the worse in the classes governing JMS between SoapUI Pro and Ready! API

then it happened between those two versions as JMS Virts was introduced. 

Best of luck. 

We appear to be having the same problem.

We used to work with SoapUI 4.6.4 and recently migrated to ReadyAPI 1.3.1 (both the 64 bit version).

In SoapUI everything workes fine, but when using ReadyAPI, error JMSFMQ6312 is showing up when executing the same step.

I've attached the logging for both SoapUI and ReadyAPI. Both give the same errors at the same point, but as you can see, the JMSFMQ6312 error is only showing up when using ReadyAPI.

Well, I found something when opening the ready-api-soapui-131.jar file and looking at the JMSConnectionHolder code. It seems there are 2 of those, but one is depricated.

The old one has the following code:

public JMSConnectionHolder(JMSEndpoint jmsEndpoint, Hermes hermes, boolean isTopicDomain, String clientID, String username, String password)

The new one is this:

public JMSConnectionHolder(JMSEndpoint jmsEndpoint, Hermes hermes, boolean isTopicDomain, String clientID)

Part of our groovy-script is the following:

def jmsConnectionHolder = new JMSConnectionHolder( jmsEndpoint, hermes, false, null ,null ,null );

So we were using the old JMSConnectionHolder.

What I did was delete the two 'null' variables we were sending so our code now read the following:

def jmsConnectionHolder = new JMSConnectionHolder( jmsEndpoint, hermes, false, null );

Bingo! The missing dll-file error has dissapeared.

Unfortunately, the next line now gives a nullpointerexception. This is the line that is now giving a problem:

Session queueSession = jmsConnectionHolder.getSession();

For info, here is our part of our groovy-script:

import com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder
import com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils
import com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSEndpoint
import hermes.Hermes
import javax.jms.*

def queue = 'jms://FAT::queue_' + context.expand( '${#Project#Omgeving}' ) + '.UQ.WEKKER_AFGEGAAN.LQ'
//def jmsEndpoint = new  JMSEndpoint("jms://FAT::queue_FPT.UQ.WEKKER_AFGEGAAN.LQ");
def jmsEndpoint = new  JMSEndpoint(queue);
def hermes = HermesUtils.getHermes( context.testCase.testSuite.project, jmsEndpoint.sessionName );
//def jmsConnectionHolder = new JMSConnectionHolder( jmsEndpoint, hermes, false, null ,null ,null );
def jmsConnectionHolder = new JMSConnectionHolder( jmsEndpoint, hermes, false, null );

Session queueSession = jmsConnectionHolder.getSession();
Queue queueSend = jmsConnectionHolder.getQueue( jmsConnectionHolder.getJmsEndpoint().getSend() );

MessageProducer messageProducer =queueSession.createProducer( queueSend );
TextMessage textMessageSend = queueSession.createTextMessage();

It's set up per the example found here: http://www.soapui.org/jms/working-with-jms-messages.html

This is the error from the log:

2015-06-05 15:41:27,742 ERROR [errorlog] java.lang.NullPointerException
java.lang.NullPointerException
    at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder.getSession(JMSConnectionHolder.java:152)
    at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder$getSession.call(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:110)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:114)
    at Script6.run(Script6.groovy:18)
    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.panels.teststeps.GroovyScriptStepDesktopPanel$RunAction$1.run(GroovyScriptStepDesktopPanel.java:263)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)