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

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JGRP-1752:
-----------------------------------------------

Petr Penicka <ppenicka at redhat.com> changed the Status of [bug 1215786|https://bugzilla.redhat.com/show_bug.cgi?id=1215786] from VERIFIED to CLOSED

> 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
>              Labels: 621
>             Fix For: 3.2.14, 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 was sent by Atlassian JIRA
(v7.2.3#72005)