MQSeries.net :: View topic - MQ pubsub brkr 'hanging' when adding a WAS MDB subscrriber

seanb

Has anyone experienced problems when using pubsub (MA0C), when a WAS MDB subscribes, which results in the pubsub broker becoming non-responsive. Also note when this occurs the MQ command server stops responding.

This is our situation.

We use pubsub on server 1. Server 1 has MQ 5.3 CSD08 with interim fixes IY67371 and IY67239 installed and runs Solaris 9. We have one QM and run one pubsub broker (as supplied with CSD08 aka MA0C) against this QM. One JMS app publishes topic-1 and one JMS app subscribes to topic-1.

We have server 2. Server 2 has MQ 5.3 CSD08 with interim fixes IY67371 and IY67239 installed and runs Solaris 9. We run one JMS app on server 2 which uses a SVRCONN channel to subscribe to topic-1 on the QM on server 1.

All works ok.

We introduce a new application on server 3. Server 3 has MQ 5.3 CSD05 and runs Solaris 8 and WAS 5.1.0. On the WAS application a MDB is used to subscribe to topic-1 on server 1 using a SVRCONN channel.

The problem is around 10 minutes after starting the publisher, the broker becomes non-responsive. This appears to happen at a time when the publishing volumes is at it's greatest. One other piece of information when the WAS subscriber went online, this happened irregulary but now occurs almost daily since the volumes have increased by 75%. We have now stopped this WAS connection and evertyhing has been ok since.

We are in the process of upgrading the WAS server 3 from MQ CSD05 to CSD08 but I'm not sure this will have any benefit as the broker is running on server 1. I know there are lots of JMS fixes in CSD08 (and CSD09).

Can anyone help?

Thanks,
Sean.