[
https://issues.apache.org/jira/browse/ARTEMIS-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425489#comment-16425489
]
ASF subversion and git services commented on ARTEMIS-1780:
----------------------------------------------------------
Commit fc32bc0b07ef37ca172dd2777701ad16bbe87ba5 in activemq-artemis's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=fc32bc0 ]
ARTEMIS-1780 Handle conversion of large ObjectMessage types
Make sure the correct buffer is used when decoding the stored Core
message that originated from the conversion of an AMQP message sent and
annotated as a JMS ObjectMessage which trips the large message boundary.
> AMQP: NPE When dispatching ObjectMessage that was handled as a Lrage 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
> 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)
