Bug 1282661 - [GSS](6.4.z) MessageDrivenComponent startDelivery/stopDelivery is not thread safe
Summary: [GSS](6.4.z) MessageDrivenComponent startDelivery/stopDelivery is not thread ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.6
Assignee: baranowb
QA Contact: Ondrej Chaloupka
URL:
Whiteboard:
Depends On:
Blocks: 1235746 1289796
TreeView+ depends on / blocked
 
Reported: 2015-11-17 01:45 UTC by James Livingston
Modified: 2019-09-12 09:19 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 11:46:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-2297 0 Major Closed MessageDrivenComponent startDelivery/stopDelivery is not thread safe 2016-11-27 09:39:42 UTC
Red Hat Issue Tracker WFLY-5596 0 Major Resolved MessageDrivenComponent startDelivery/stopDelivery is not thread safe 2016-11-27 09:39:42 UTC

Description James Livingston 2015-11-17 01:45:13 UTC
Bug 1159572 made a change to prevent MDBs being activated or deactivated multiple times, but it is not thread safe. A volatile boolean is used for the flag, but there is no protection against multiple threads invoking the methods simultaneously.

Comment 1 James Livingston 2015-11-17 01:46:54 UTC
I do not think it is possible to trigger this bug without a custom extension, since the shipped code only has one path into it and cannot trigger the race condition.

With a custom/third-party extension, it is possible to trigger.

Comment 8 JBoss JIRA Server 2016-01-10 23:49:02 UTC
James Livingston <jlivings> updated the status of jira JBEAP-2297 to Coding In Progress

Comment 9 JBoss JIRA Server 2016-01-10 23:49:55 UTC
James Livingston <jlivings> updated the status of jira JBEAP-2297 to Resolved

Comment 10 JBoss JIRA Server 2016-01-10 23:50:30 UTC
James Livingston <jlivings> updated the status of jira JBEAP-2297 to Reopened

Comment 11 JBoss JIRA Server 2016-01-10 23:50:34 UTC
James Livingston <jlivings> updated the status of jira JBEAP-2297 to Coding In Progress

Comment 12 Ondrej Chaloupka 2016-01-20 22:26:41 UTC
Byteman rule based reproducer. Not an integration, only checks if method startDelivery is synchronized.


git clone git:ochaloup/byteman.git --branch dtest-instrumentation-enhancement
cd byteman
mvn install
cd -

git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git --branch WFLY-5596-reproducer

export JBOSS_HOME=path/to/jboss
export JBOSS_HOME_1="$JBOSS_HOME"
export JBOSS_HOME_2="$JBOSS_HOME"
export JBOSS_HOME_3="$JBOSS_HOME"
export JBOSS_HOME_4="$JBOSS_HOME"

cd eap-tests-hornetq/jboss-hornetq-testsuite
mvn clean install -Dmaven.test.skip.exec
cd common-tests
mvn clean install -Dtest=DuplicateMessageTestCase

Comment 14 JBoss JIRA Server 2016-06-14 11:38:11 UTC
Jiri Pallich <jpallich> updated the status of jira JBEAP-2297 to Closed

Comment 15 Petr Penicka 2017-01-17 11:46:00 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 16 Petr Penicka 2017-01-17 11:47:35 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.


Note You need to log in before you can comment on or make changes to this bug.