Re: [ajug-members]: clustering websphere mq

I'll try a little bit more...

when i define my broker for the queue manager it needs to be remote instead of local. I've never worked with websphere mq before so please bare(sp) with me.

----- Original Message -----

From: dave wible

To: ajug-members@ajug.org

Sent: Wednesday, May 12, 2004 2:32 PM

Subject: [ajug-members]: clustering websphere mq

Good afternoon. My second question for those of you at home, counting.

I've never used the jms api nor websphere mq. So... I've been tasked with an issue. We have a change to our configuration where we are now clustering our queues. Before the QueueManager was able to resolve the queue b/c it was local but now, as I understand it, it is no longer local so the QueueConnectionFactory doesn't return a valid queue connection? Maybe we don't have the messageClient on the loadbalancer box? Or are there settings for the queueconnection factory that have to be modifed b/c in our deployment so it knows that it needs to find a remote queue source?

the config mgr who's been working on this said that the queuemanager name needs to be blank and it should work.

here is some error text:

Unable to start MDB Listener LoadTransactionListener, JMSDestination jms/LoadTransactionsQ : javax.jms.JMSException: MQJMS2008: failed to open MQ queue

Thanks,

David W