SoapUI and JMS MQ 7.0 Connections

[PChilcott]

Hi

We have a mock service in SoapUI that puts messages on a JMS queue (Websphere MQ v7.0.1 as the provider) via a test step i.e. the test step in invoked via the groovy script in the mock service. This mock service is started via command line mock runner and runs on a dedicated server.

During testing we have noticed that JMS connections opened by the test step in mock service are not closed after it has finished. This results in a large number of SYSTEM.DEF.SVRCONN channel connections running. Do we need to do any configuration in the test step for these connections to be closed? We have already tried setting a timeout in test step to 10 seconds.


Thanks

[SmartBear Support]

Hi,

hmm.. this sounds like an old issue - which soapUI Pro version are you using?

regards!

/Ole
SmartBear Software

[PChilcott]

Hi Ole

We are using SoapUI Pro 4.0.0, Build dist-131-2011-06-14, Build Date 2011/06/14.


Thanks

[PChilcott]

Hi

We have tested today with SoapUI pro version 4.0.1 Build dist-142-2011-09-14, Build Date 2011/09/14 13:38 and the issue still persists.


Thanks

[PChilcott]

We have tried today with SoapUI-Pro 4.0.2 Snapshot and the issue still persists. For the open MQ channels to be closed we had to quit soapui.

Can someone from the development team confirm that this is a known issue with SoapUI Pro and are there any plans for future fix?


Thanks

[SmartBear Support]

Hi,

I've filed this as a bug internally - hopefully we will get around to looking at it for the upcoming 4.5 release.

regards,

/Ole
SmartBear Software

[PChilcott]

Hi /Ole

We have tried today with SoapUI 4.5 Beta release and the issue still persists. MQ channels remain open even after the tests have finished execution. Like with older versions, the only way to close these channels is to close SoapUI.


I suspect the issue has not yet been fixed since the release notes don't say any thing about MQ related bugs. Can you please confirm this?


Thanks

[PChilcott]

Hi

This is a very critical issue for us and we were hoping for it to be fixed in release 4.5, however our tests indicate that the issue still persists in the latest beta release. We have around 100 SoapUI Pro licenses and will really appreciate if there is a work around to this issue that doesn't involve restarting SoapUI as this has a strong impact on our over all solution.

We are open to making changes to the source code if the support team can guide us in that direction. Can we please get some help?


Thanks

[SmartBear Support]

Hi,

we have checking this issue and we cannot reproduce it so far. Can you please send us a project file to smartbear-sweden-support@smartbear.com so we can investigate.

Thanks

nebojsa
SmartBear Software