Posted: Wed Jan 18, 2006 8:48 am Post subject: WebSphere MQ JMS provider with WAS 5
Apprentice
Joined: 14 Jun 2002 Posts: 31 Location: Kansas City
I have very little experience with JMS and Websphere application server and need some advice. Recently we implemented a vender product that runs under WAS 5 and uses MQ JMS. The issue is, when I cycle the queue manager that the listener is connected to, when the queue manager restarts, the application remains disconnected and we have to recycyle the message listener in WAS. I assume that the responcibility re-establishing the connection is that of the application. Is this correct, or can something be set in the WAS JMS listener port definition to retry this connection at certain intervals, or other WAS properties?
As we implement more and more JMS applications I am concerned that any time I need to recycle the queue manager that I will have to coordinate with the WAS administrator to cycle the listeners.
There was a similar patch in FP3 for WAS 5.1 for LDAP connections - which you *really* don't want to go stale with no way of recovery short of restart. _________________ I am *not* the model of the modern major general.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum