JMS and MqSeries

[Madere]

Hi all.

I want, if it is possible, to connect to a MqSeries Queue, which is on a remote server, using JMS.

I know there are MqSeries JMS API's but I wont/cant use these. With these JMS API I can send messages to the MqSeries Queue without any problem.
So I have to fall back on pure JMS API's.

I have tried it so far, but no luck. I am getting a JMSException:
"Could not create session, connection may be dropped".

When I connect to a JMS Queue on my local machine with the same portnumber and Queue Name, I have no problems in connecting. I can even send a message.

Only when I try to connect to the remote MqSeries Queue, I get this problem.

I think I get this exception because the MqSeries Queue is NOT JMS, so therefore a session cant be build.

So therefore I am looking for another way to connect to the MqSeries Queue's using JMS (if there is a way) or for the correct JMS implementation.

Any help is welcome. No questions please about why not using the MqSeries JMS API, it is simple not possible to use them.

 

[Diancecht]

why not using the MqSeries JMS API?

Now, seriously, sounds like a configuration problem at serverside.

http://publib.boulder.ibm.com/infoc...m.websphere.nd.doc/info/ae/ae/ucli_pqcfm.html

Cheers,
Dian

 

[Madere]

Well thnx for the answer.

But I am NOT using WebSphere, so I dont have the possibilties to configure my application in the way described.

I am using a simple Java Programm from Eclipse just using JMS.
If possible, where to enter the Channel info in the JMS connection or session info?

 

[timw]

Unfortunately, the JMS API is simply that:- It is only an interface. To communicate with any given implementation of that API you need to use the classes provided by the MQ vendor. So if you want to use MQ Series remotely, you'll need to be able to see their JMS classes from the client.

For example, I've used JBossMQ remotely. I needed to put the jbossall-client.jar on the client's classpath because it includes JBoss's implementation of the JMS interfaces needed to talk to JBossMQ.

Sorry if that's no help, but it's a statement of fact.

Tim