From issues-return-28168-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Tue May 8 16:43:09 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B46E5180674 for ; Tue, 8 May 2018 16:43:08 +0200 (CEST) Received: (qmail 79632 invoked by uid 500); 8 May 2018 14:43:07 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 79623 invoked by uid 99); 8 May 2018 14:43:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2018 14:43:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7059618084E for ; Tue, 8 May 2018 14:43:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id siOHhuNEuLus for ; Tue, 8 May 2018 14:43:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4ED825FB66 for ; Tue, 8 May 2018 14:43:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 82CAAE010F for ; Tue, 8 May 2018 14:43:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 36FC621299 for ; Tue, 8 May 2018 14:43:00 +0000 (UTC) Date: Tue, 8 May 2018 14:43:00 +0000 (UTC) From: "clebert suconic (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARTEMIS-1780) AMQP: NPE when dispatching ObjectMessage that was handled as a Large Message MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ARTEMIS-1780?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 467490#comment-16467490 ]=20 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=C2=A0fc32= bc0b07ef37ca172dd2777701ad16bbe87ba5. The original ID for the commit was=C2= =A0 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 Mess= age > -------------------------------------------------------------------------= --- > > 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 mess= age and is converted to / from Core the dispatch of the message throws an N= PE seemingly because the ServerJMSObjectMessage and converter code is calli= ng the wrong method to get the underlying buffer.=C2=A0 The other message t= ypes go through a getDataBuffer method while the ObjectMessage handler code= uses a getBodyBuffer that doesn't account for the case of the message bein= g "Large" -- This message was sent by Atlassian JIRA (v7.6.3#76005)