1 of 1 people found this helpful
My guess is that a few of the JMS sessions used by your MDB on one of the nodes are sucking up all the messages before the others have a chance to get any. See this for an explanation of how to modify the client buffering on the server-side. You can also do the same thing from the MDB-side by using the consumerWindowSize activation configuration property.
thank you very much for this prompt reply.
We tried the setting consumer-window-size=0 but the behavior does not change.
1 AS consumes 15 messages, then another one consumes 15 messages, and so on... (ok for peaks of activity but poor laod balancing during normal activity).
Maybe I did not understand the meaning of the consumer-window-size setting.I though that the no-buffering would be what we need.
Any other ideas are welcome!