activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1780) AMQP: NPE when dispatching ObjectMessage that was handled as a Large Message
Date Tue, 08 May 2018 14:43:00 GMT

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

clebert suconic commented on ARTEMIS-1780:
------------------------------------------

[~martyntaylor] I don't understand the issue. looking at the PR #1985 this was regular business...
the PR rebased and merged Tim's commit as fc32bc0b07ef37ca172dd2777701ad16bbe87ba5. The original
ID for the commit was 

d4cd0518a6a310931a0d7ae5b4112e72faec7c65 but it was rebased before merge to avoid merge commits,
something we do regularly with the ./scripts/merge-PR.sh

> AMQP: NPE when dispatching ObjectMessage that was handled as a Large Message
> ----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1780
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1780
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.5.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Major
>             Fix For: 2.5.1
>
>
> When JMS ObjectMessage is sent which end up being treated as a large message and is converted
to / from Core the dispatch of the message throws an NPE seemingly because the ServerJMSObjectMessage
and converter code is calling the wrong method to get the underlying buffer.  The other message
types go through a getDataBuffer method while the ObjectMessage handler code uses a getBodyBuffer
that doesn't account for the case of the message being "Large"



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

Mime
View raw message