[
https://issues.apache.org/jira/browse/ARTEMIS-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660772#comment-16660772
]
ASF subversion and git services commented on ARTEMIS-2135:
----------------------------------------------------------
Commit f4c93a2860f384ce87e3589012e5278399c550c3 in activemq-artemis's branch
refs/heads/master from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=f4c93a2 ]
ARTEMIS-2135 Test multiple core consumers receiving amqp messages
This test can verify an issue fixed by the commit:
7a463f038ae324f2c5c908321b2ebf03b5a8e303 (ARTEMIS-2096)
The issue was reported later by users where messages
sent by amqp clients are having their body size
randomly being zero when received by multiple core
consumers.
This was also fixed on commit 48e0fc8f42346d96bc809593a150e05a586787e but that
was exclusively on 2.6.x branch.
> 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)
