Build 37 nightly, Jan. 05. OEL5 machines.
The build was installed on three machines. DAS plus one instance, on asqe-x2250-st5, the other two instances on asqe-x2250-st6 & asqe-x2250-st7. In the cluster, the Stress Application, RichAccess, was deployed. Against each instance in the cluster, a test client was running and sending http requests at a rate that is equivalent to 100 simultaneous users per instance. MQ was set in Embedded mode. Heap size was 768Mb.
After about one hour of running, either an Out of Memory (OOM) error occurred or the following messages were posted in the MQ log:
[05/Jan/2011:07:31:19 PST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,email@example.com:22300,null] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4120]: Can not store message 9048323-10.133.184.161(ca:3d:25:9a:7a:46
)-22300-1294241479417 on destination richAppTopic [Topic]. The destination message count limit (maxNumMsgs) of 100000 has been reached.
It looks like the OOM condition or "message count limit has been reached" issues were caused by the same problem. It was observed that the MQ messages were slowly consumed.
For this reason, we believe, the stress Test crashed on this setup.