October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-151) Protocol and namespace values are duplicated in the code

by Kevin Conner (JIRA)

Protocol and namespace values are duplicated in the code -------------------------------------------------------- Key: JBTM-151 URL: http://jira.jboss.com/jira/browse/JBTM-151 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 Protocol valies and namespaces are duplicated in parts of the WS-TX code, these should only exist in the appropriate constants interface. -- 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

18 years, 2 months

1
6
0 / 0

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

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=all ] Clebert Suconic updated JBMESSAGING-355: ---------------------------------------- Attachment: race-condition.log I have updated the file with few enters and some comments like the following to easily find where the racing condition happens: ****** what happens next ******* > 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.0.2.CR1 > > 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

18 years, 2 months

1
0
0 / 0

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

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=all ] Clebert Suconic updated JBMESSAGING-355: ---------------------------------------- Attachment: (was: race-condition.log) > 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.0.2.CR1 > > 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-154) SOAP processor access should be serialised

by Kevin Conner (JIRA)

SOAP processor access should be serialised ------------------------------------------ Key: JBTM-154 URL: http://jira.jboss.com/jira/browse/JBTM-154 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.2 Reporter: Kevin Conner Assigned To: Kevin Conner The wsat/wsba low level SOAP processors should have serialised access to the singleton. -- 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

18 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-155) The ba coordinator TxState is unused

by Kevin Conner (JIRA)

The ba coordinator TxState is unused ------------------------------------ Key: JBTM-155 URL: http://jira.jboss.com/jira/browse/JBTM-155 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 The BA coordinator TxState is unused and should be removed. -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-153) wsat/Participant should be refactored sh that it can be shared with the wsat11 code.

by Kevin Conner (JIRA)

wsat/Participant should be refactored sh that it can be shared with the wsat11 code. ------------------------------------------------------------------------------------ Key: JBTM-153 URL: http://jira.jboss.com/jira/browse/JBTM-153 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 Refactor the Participant to allow sharing with wsat11 code. -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-152) wsarjtx ba terminator uses the AT NotificationType instead of the wsarjtc NotificationType

by Kevin Conner (JIRA)

wsarjtx ba terminator uses the AT NotificationType instead of the wsarjtc NotificationType ------------------------------------------------------------------------------------------ Key: JBTM-152 URL: http://jira.jboss.com/jira/browse/JBTM-152 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 The wsarjtx low level serialisation is using the NotificationType defined by the AT schema instead of the one associated with the wsarjtx namespace. -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-150) WS-A 2005, Non anonymous ReplyTo should be executed on a background thread if there is no FaultTo

by Kevin Conner (JIRA)

WS-A 2005, Non anonymous ReplyTo should be executed on a background thread if there is no FaultTo ------------------------------------------------------------------------------------------------- Key: JBTM-150 URL: http://jira.jboss.com/jira/browse/JBTM-150 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 A non anonymous ReplyTo with no FaultTo can be run on a background thread. -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-148) Add method to SoapDetails to return the SOAP mustUnderstand value.

by Kevin Conner (JIRA)

Add method to SoapDetails to return the SOAP mustUnderstand value. ------------------------------------------------------------------ Key: JBTM-148 URL: http://jira.jboss.com/jira/browse/JBTM-148 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 WSTX1.1 makes use of the SOAP mustUnderstand value -- 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

18 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-149) URI values should be trimmed.

by Kevin Conner (JIRA)

URI values should be trimmed. ----------------------------- Key: JBTM-149 URL: http://jira.jboss.com/jira/browse/JBTM-149 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 URI and attributed URIs should have their value trimmed. -- 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

18 years, 2 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006