Managing High load failure scenarios for the Aggregation node in WMB message flows A common scenario in WMB message flows is when the aggregation message flows call multiple validation services which are supposed to return a reply within 2 minutes. In normal scenarios, 10 to 50 requests are handled per minute. In high volume load scenarios, more than 100 requests are received per minute which leads to the failure of aggregation message flows. The aggregate replies from validation services will pile up on the aggregation reply queues making any new requests impossible. The piled up requests have to be cleared and only then the failed requests can be retried using a retry message flow which reads the aggregation requests from the input backout queue and processes them once again. This issue requires attention from IBM and can be fixed by having queue depth monitors and triggers on the aggregate request and reply queues. I would like to bring this issue to the notice of IBM
Configuring syslog.user in /etc/services of Unix The syslog.user log file of Websphere message broker can be upto 2 Gb in size. This log file should be configured in the conf files present in the /etc/services of Unix The inetd.conf contains the folder where the syslog.conf will be present and syslog.conf file contains the file size of syslog.user. A message broker restart was necessary after configuring this file. The same configurations apply in AIX also.