[jboss-jira] [JBoss JIRA] (JGRP-1752) Concurrent message headers modification causes that message is never sent

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928502#comment-12928502 ] 

Bela Ban edited comment on JGRP-1752 at 12/4/13 6:27 AM:
---------------------------------------------------------

https://github.com/belaban/JGroups/commit/1ded73104b701b448f06fb0a8eb2077c0fbb0347
                
      was (Author: belaban):
    1ded73104b701b448f06fb0a8eb2077c0fbb0347
                  
> Concurrent message headers modification causes that message is never sent
> -------------------------------------------------------------------------
>
>                 Key: JGRP-1752
>                 URL: https://issues.jboss.org/browse/JGRP-1752
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.4.1
>            Reporter: Radim Vansa
>            Assignee: Bela Ban
>             Fix For: 3.4.2, 3.5
>
>
> Under some circumstances the TP protocol may try to add the TP header to message twice concurrently.
> This happens for example when the stable message triggers retransmission while the message has been sent right now.
> This may result in ArrayOutOfBoundException in Headers._putHeader and/or subsequent NullPointerException in Headers.size(). The retransmission attempt always fails, the message is never delivered. Moreover, keeping this (and possibly following) messages in the transmission table can lead to OOME.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira