Bug 1080806
| Summary: | HornetQTaskClientConnector not acknowledging received messages | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Martin Weiler <mweiler> | ||||||
| Component: | jBPM 5 | Assignee: | Kris Verlaenen <kverlaen> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Marek Baluch <mbaluch> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | BRMS 5.3.1 | CC: | mbaluch, mhernon, nwallace | ||||||
| Target Milestone: | GA | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1081515 (view as bug list) | Environment: | |||||||
| Last Closed: | 2025-02-10 03:35:28 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1080634, 1081515 | ||||||||
| Attachments: |
|
||||||||
Created attachment 878982 [details]
Patch proposal
The fix needs to be applied to BaseHornetQTaskServer as well:
+ message.acknowledge();
+ session.commit();
Verified in BRMS 5.3.1.P06 roll-up patch on EAP 6.2.3 (full-build). This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Created attachment 878894 [details] Screenshot of jconsole and heap dump after a load test with human task process Description of problem: HornetQTaskClientConnector is handling receipt of messages, but is neither using automatic message acknowledgement, nor is it calling message.acknowledge(). As a result, messages remain in the queue and thus in memory (see attached screenshot of jconsole and heap dump after running some load tests). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run jBPM process with human tasks 2. Connect to the BRMS server with jconsole, and check the MessageCount and DeliveryCount attributes of the tasksQueue. 3. If messages were ack'd, the values of these attributes should be 0 Actual results: Messages not ack'd and remain in the tasksQueue Expected results: Messages are removed from the queue after successful handling. Additional info: