Bug 1159572 - Duplicate message deliveries when start an MDB twice via CLI
Summary: Duplicate message deliveries when start an MDB twice via CLI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: CR2
: EAP 6.4.1
Assignee: Chao Wang
QA Contact: Miroslav Novak
URL:
Whiteboard:
Depends On:
Blocks: eap641-payload
TreeView+ depends on / blocked
 
Reported: 2014-11-01 16:08 UTC by Tyronne Wickramarathne
Modified: 2019-07-11 08:19 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 09:58:55 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-4470 0 Major Resolved Duplicate message deliveries when start an MDB twice via CLI 2017-06-22 17:40:44 UTC

Description Tyronne Wickramarathne 2014-11-01 16:08:25 UTC 
Description of problem:
A singleton MDB delivers duplicate messages when start-delivery() is invoked twice while the message being delivered


Version-Release number of selected component (if applicable):
JBoss-EAP-6.3.1


Steps to Reproduce:
1. Create a producer, which keeps sending messages for every second
2. Deploy a singleton consumer MDB
3. Invoke start-delivery() method on the MDB while the messages being delivered

Actual results:
MDB delivers duplicate messages

Expected results:
MDB needs to ignore start-delivery() call if the MDB has already been started.

Additional info:
Comment 6 Rostislav Svoboda 2015-04-23 11:11:28 UTC 
Re-acking after "qa_ack flag reset for and jboss-eap-6.4.0 and jboss-eap-6.4.z items" cleanup.
Comment 8 Miroslav Novak 2015-05-18 06:51:02 UTC 
Verified in EAP 6.4.0.CP1.CR2 using MDBTestCase. Thanks for the test!
Comment 9 Petr Penicka 2017-01-17 09:58:55 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 10 Petr Penicka 2017-01-17 10:00:04 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Note You need to log in before you can comment on or make changes to this bug.