January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMESSAGING-327) Improve concurrency for acknowledgement

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-327?page=all ] Ovidiu Feodorov closed JBMESSAGING-327. --------------------------------------- Resolution: Won't Fix Fix Version/s: (was: 1.2.1) 1.2.0.Beta2 > Improve concurrency for acknowledgement > --------------------------------------- > > Key: JBMESSAGING-327 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-327 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Beta2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Improve concurrency in acknnowledgment by using ConcurrentHashSet for deliveries and removing delivery lock -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-355) Remove possibility of delivery race conditions

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=all ] Ovidiu Feodorov reopened JBMESSAGING-355: ----------------------------------------- > Remove possibility of delivery race conditions > ---------------------------------------------- > > Key: JBMESSAGING-355 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-355 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Beta2 > > Attachments: race-condition.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently race conditions can occur on message delivery where the delivery is acknowledged or cancelled before the call to handle has returned. > In ChannelState we defensively program against this by synchronizing on the returned delivery and by dealing with the situation where the delivery does not exist in the channel state and ignoring. > See ChannelSupport::deliver() and ChannelState.cancelDelivery. > This approach has the following problems: > Complexity of code to maintain and understand. > Where acks return quickly we are likely to get contention on the lock in ChannelSupport::deliver, thus reducing throughput. > A much simpler solution enables us to remove the possibility of such race conditions and remove the corresponding lock contention. > This can be done by adding a confirm() method on Delivery. > When the receiver receives the message in it's handle() call, before dispatching the message it calls Delivery::confirm. This results in the channel adding the delivery to the channel state. Thus we can be assured that the delivery exists before any acknowledgment or cancellation comes in. > This is a very simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-355) Remove possibility of delivery race conditions

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=all ] Ovidiu Feodorov closed JBMESSAGING-355. --------------------------------------- Fix Version/s: 1.2.0.Beta2 (was: 1.2.1) Resolution: Won't Fix > Remove possibility of delivery race conditions > ---------------------------------------------- > > Key: JBMESSAGING-355 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-355 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Beta2 > > Attachments: race-condition.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently race conditions can occur on message delivery where the delivery is acknowledged or cancelled before the call to handle has returned. > In ChannelState we defensively program against this by synchronizing on the returned delivery and by dealing with the situation where the delivery does not exist in the channel state and ignoring. > See ChannelSupport::deliver() and ChannelState.cancelDelivery. > This approach has the following problems: > Complexity of code to maintain and understand. > Where acks return quickly we are likely to get contention on the lock in ChannelSupport::deliver, thus reducing throughput. > A much simpler solution enables us to remove the possibility of such race conditions and remove the corresponding lock contention. > This can be done by adding a confirm() method on Delivery. > When the receiver receives the message in it's handle() call, before dispatching the message it calls Delivery::confirm. This results in the channel adding the delivery to the channel state. Thus we can be assured that the delivery exists before any acknowledgment or cancellation comes in. > This is a very simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-327) Improve concurrency for acknowledgement

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-327?page=all ] Ovidiu Feodorov reopened JBMESSAGING-327: ----------------------------------------- > Improve concurrency for acknowledgement > --------------------------------------- > > Key: JBMESSAGING-327 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-327 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Improve concurrency in acknnowledgment by using ConcurrentHashSet for deliveries and removing delivery lock -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3950) Change ejb2 invoker to be the unified invoker

by Dimitris Andreadis (JIRA)

Change ejb2 invoker to be the unified invoker --------------------------------------------- Key: JBAS-3950 URL: http://jira.jboss.com/jira/browse/JBAS-3950 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Tom Elrod Fix For: JBossAS-4.2.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-386) Isolate JBossMQ-specific tests and make sure they pass

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-386?page=all ] Ovidiu Feodorov closed JBMESSAGING-386. --------------------------------------- Resolution: Duplicate Issue Fix Version/s: (was: 1.2.1) 1.2.0.Beta2 > Isolate JBossMQ-specific tests and make sure they pass > ------------------------------------------------------ > > Key: JBMESSAGING-386 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-386 > Project: JBoss Messaging > Issue Type: Sub-task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta2 > > > Move them inside the JBossMQ project as functional tests -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-386) Isolate JBossMQ-specific tests and make sure they pass

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-386?page=all ] Ovidiu Feodorov reopened JBMESSAGING-386: ----------------------------------------- > Isolate JBossMQ-specific tests and make sure they pass > ------------------------------------------------------ > > Key: JBMESSAGING-386 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-386 > Project: JBoss Messaging > Issue Type: Sub-task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta2 > > > Move them inside the JBossMQ project as functional tests -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-150) TCK sould test Messaging, and not JBossMQ, by default

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-150?page=all ] Ovidiu Feodorov closed JBMESSAGING-150. --------------------------------------- Resolution: Done Fix Version/s: (was: 1.2.0.CR1) 1.2.0.Beta2 > TCK sould test Messaging, and not JBossMQ, by default > ----------------------------------------------------- > > Key: JBMESSAGING-150 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-150 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Priority: Minor > Fix For: 1.2.0.Beta2 > > > Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. > See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. > All TCK-related Messaging configuration files and build scripts are in https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to j2eetck-mods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-385) Generalize jboss testsuite JMS tests to work with both Messaging and JBossMQ (where possible) and make sure they pass

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-385?page=all ] Ovidiu Feodorov closed JBMESSAGING-385. --------------------------------------- Resolution: Duplicate Issue Fix Version/s: (was: 1.2.1) 1.2.0.Beta2 > Generalize jboss testsuite JMS tests to work with both Messaging and JBossMQ (where possible) and make sure they pass > --------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-385 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-385 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta2 > > > More details on how to do that: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=72570 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-385) Generalize jboss testsuite JMS tests to work with both Messaging and JBossMQ (where possible) and make sure they pass

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-385?page=all ] Ovidiu Feodorov reopened JBMESSAGING-385: ----------------------------------------- > Generalize jboss testsuite JMS tests to work with both Messaging and JBossMQ (where possible) and make sure they pass > --------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-385 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-385 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta2 > > > More details on how to do that: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=72570 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007