Red Hat Bugzilla – Bug 780438
QS monitoring_action does not report passed messages correctly
Last modified: 2013-03-13 00:56:33 EDT
Three messages (numbers 3,14,23) are sent to MVELMonitoringAction that is set to report messages satisfying condition >5. As the result messages 14 and 23 should be stored in mbean as described in the readme file, but what is stored there is a duplicate of the last message, 23. The number of stored messages is correct (verified with more messages), but all the messages are duplicates of the last one passed.
There are a number of concurrency issues in MVELMonitoringAction/MVELMonitor/MonitoringPatternBean but this particular issue is caused by the reuse of the MonitoringPatternBean which contains the message value. All entries in the list refer to the same instance.
Link: Added: This issue relates to JBESB-3602
Fixed in ESB project.
tcunning@localhost:product]$ svn commit
Transmitting file data ..
Committed revision 36947.
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2871
The MVELMonitoringAction was storing the correct number of messages but each of them was just a duplicate of the very last message passed. This bug was caused by the reuse of the MonitoringPatternBean (which contains the message value) and which resulted in every enty in the list referring to the same instance. A code fix has been applied and, as a result, the messages are now stored correctly.
Verified in SOA 5.2 ER4.