[ 
https://issues.apache.org/jira/browse/ARTEMIS-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659986#comment-16659986
 ] 

ASF GitHub Bot commented on ARTEMIS-2135:
-----------------------------------------

GitHub user gaohoward opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2386

    ARTEMIS-2135 Test multiple core consumers receiving amqp messages

    This test can verify an issue fixed by the commit:
    48e0fc8f42346d96bc809593a150e05a586787ee (ARTEMIS-2135)
    (note the upstream fix is ARTEMIS-2096)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gaohoward/activemq-artemis d_26x_2034fix2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2386.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2386
    
----
commit 07355b1fa6f1d20a50f130df48dd8fe006932e54
Author: Howard Gao <howard.gao@...>
Date:   2018-10-19T13:40:33Z

    ARTEMIS-2135 Test multiple core consumers receiving amqp messages
    
    This test can verify an issue fixed by the commit:
    48e0fc8f42346d96bc809593a150e05a586787ee (ARTEMIS-2135)
    (note the upstream fix is ARTEMIS-2096)

----


> NPE in AMQPMessage getPriority
> ------------------------------
>
>                 Key: ARTEMIS-2135
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2135
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>    Affects Versions: 2.6.3
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>            Priority: Major
>             Fix For: 2.6.4
>
>
> getHeader may eventually return null if AMQPCoreConverter is used in 
> multi-thread.
>  
>  
> This doesn't affect master currently as that was fixed at ARTEMIS-2096.
>  
> I am adding a test in master, and applying a fix in 2.6.x only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to