Websphere MQ

[tom.hargrave]

Hi, I'm trying to get a connection to websphere MQ. I have installed the IBM bundles and configured the spring config to reference the remote queue manager.

At runtime I'm getting this error => java.lang.ClassNotFoundException: javax.net.ssl.HandshakeCompletedListener not found by com.ibm.msg.client.osgi.wmq

None of the IBM bundles import javax.net.ssl and I can't really re-bundle them?

Has anyone managed to get a connection working to WMQ from servicemix/fuse - 4 ?

Any help is much appreciated.

Many thanks in advance, Tom

[janstey]

Yep, I have used WMQ and ServiceMix in the past. What version of WMQ and ServiceMix are you using? You may find the sample code and instructions posted by one of our consultants helpful http://lowry-techie.blogspot.com/2010/11/camel-integration-with-websphere-mq.html

Cheers,

Jon

[tom.hargrave]

Hi, many thanks for your reply.

I already found (and followed) this article that sadly didn't work for me.

FuseESB Version: apache-servicemix-4.4.1-fuse-01-13

WMQ Version: 7.0.1.1, 7.0.1.3 and 7.0.1.5 (all gave same error).

WMQ Version: 7.0.1.3 and 7.0.1.5 would even install all the IBM OSGI bundles?

Is there something else I'm not doing (or doing wrong) ??

Any help is very much appreciated.

Best regards, Tom

[tom.hargrave]

TYPO: WMQ Version: 7.0.1.3 and 7.0.1.5 would not even install all the IBM OSGI bundles?

[janstey]

Not really sure what is happening there... could you paste your full stack trace to give a little more context?

Some things to try:

1. make sure that package is actually available

packages:exports | grep javax.net.ssl

2. try turning on dynamic imports on the bundle that can't grab the ssl package

dev:dynamic-import

Cheers,

Jon

Edited by: janstey on Feb 21, 2012 1:57 PM

[tom.hargrave]

Hi Jon, many thanks again for your reply.

I can see the javax.net.ssl bundle but get a "Unknown protocol: inputstream" error when trying to activate dynamic imports on the IBM bundle.

I attach a screen shot of the console and also the log files.

I really appreciate you helping me.

Many thanks in advance....

Tom

[janstey]

Tom,

OK, something else to try... sometimes when dealing with odd classloading issues, it helps to try out another OSGi framework. Felix and Equinox both implement the spec but approach things differently under the hood. So, to try out Equinox instead of Felix open up etc/config.properties and make the following change:

karaf.framework=equinox

Make sure to also delete the "data" dir before start the ESB again.

I think I'll need to actually try this for myself if this doesn't work

Cheers,

Jon

[tom.hargrave]

Hi Jon, great news.... it worked.... for WMQ 7.0.1.1 IBM bundles (error for 7.0.1.5) but I can live with 7.0.1.1 just fine for now.

I'm not an OSGI framework expert - are there reasons/issues with using equinox? I'm guessing Felix is preferred default for a reason?

Many thanks once again....

[janstey]

Ah glad you are set but still would be nice to fix this for Felix... both frameworks are good IMHO but for Felix we have several engineers working on that project so it allows us to actually fix framework issues rather than just working around them. Also, Equinox is not as heavily tested as Felix in our distributions.

Let us know if you hit this again or require this fixed in Felix.

Cheers,

Jon

[tom.hargrave]

Many thanks Jon,

I think it would be preferable to have this working in Felix - I'd sooner have a more default and supported platform if I can. Also I'm sure there may be other businesses that have an integration need with WMQ.

Here is my simplified camel config if that helps - a simple copy from ActiveMQ to WMQ:-

Best regards, Tom

[janstey]

Hi Tom,

I've created a ticket for this in our issue tracker so we don't lose track of it.

http://fusesource.com/issues/browse/ESB-1645

Feel free to vote or watch the issue for updates.

Cheers,

Jon