Posted: Fri Jul 12, 2013 11:19 am Post subject: MQ reader count increasing, when using activation spec
Novice
Joined: 06 Apr 2006 Posts: 10
We have an MDB that is deployed in WAS. The MDB consumes messages using Activation Spec and Queue configurations. All configurations were made using the default values for session management, etc.
In-spite of this the provider (MQ) of the messages see that their MQ Queue reader count are increasing over time and reaching upto 501 on each of their queues.
The MDB uses the EJB version 3 with annoations. It just reads the messages (onMessage) and does nothing (no much processing, just like draining the queue).
Our infrastructure is a clustered env with two app servers and one MDB application each server consumes messages from same queues. One actication spec for each server connectivity to same Queue manager and same queue.
Server Thread Pool properties
WMQJCAResourceAdapter wmqJcaRaThreadPoolDescription 5 25
Activation spec Advanced properties
Rescan interval - 5000 milli secs
Maximum server sessions - 10
Start timeout - 10000 milli secs
Server session pool timeout - 30000 milli secs
Number of sequential delivery failures before suspending endpoint - 0
Depending on the setting of your share conversations on the channel....
Assuming your share conversations is set to 0 or 1
You will need just for the MDB inbound (number of MDB instances +1 connections)
Add to that the outbound connection of the MDB and you have (2*MDB instances +1)
Add to that all other concurrent outbound connections from WAS ... at any time (peak).
Oh and don't forget to add any other channel connections.... (yes that includes qmgr 2 qmgr and all autodefined cluster connections...)
This way you get an idea of your maxchannels. Multiply by 2 or 3 and modify the settings. Bounce the qmgr.
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