Well, I posted a case and got a workaround: replace commons-beanutils-1.8.3.jar in {ReadyAPI install}/lib with commons-beanutils-1.7.0.jar from {SoapUI Pro install}/lib.
Seems to do the trick :-)
Unfortunately this only prolonged the problem to another line.
The constructor you were using previously allowed you to create a connection directly to your broken when creating the connectionHolder. The constructor you are using now prolongs the creation of that connection, but since the connection is not yet created there is no session to get. You can verify this by running jmsconnectionHolder.createConnection() right after creating it with your current constructor.
So we're not there yet unfortunately. I'm just about to try some debuggin on this, i'll get back to this thread soon with my findings.
Two kinds of news.
The bad news:
I haven't been able to fix the problem
The good news:
I have downloaded a WebSphere 7.5 trial and reproduced your exact problems and can tinker with it to see if i can find a workaround for it.
I'll be in touch.
Thanks. Looking forward to your findings.
This morning, I extracted the properties ReadyAPI uses to create the connection. As can be seen, the values of XMSC_WMQ_CONNECTION_MODE and XMSC_WMQ_QUEUE_MANAGER are not correctly set.
When doing the same in SoapUI, both properties are correctly set.
I've attached the properties. I've used the following statement to see them;
def connectionFactory = hermes.getConnectionFactory();
log.info connectionFactory;
Any status updates regarding this?
