Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 463A7E45C for ; Wed, 9 Jan 2013 17:55:59 +0000 (UTC) Received: (qmail 58623 invoked by uid 500); 9 Jan 2013 17:55:58 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 58580 invoked by uid 500); 9 Jan 2013 17:55:58 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 58571 invoked by uid 99); 9 Jan 2013 17:55:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 17:55:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of james.mk.green@gmail.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 17:55:52 +0000 Received: by mail-qc0-f182.google.com with SMTP id k19so1716308qcs.41 for ; Wed, 09 Jan 2013 09:55:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=LU/BwoW9LftOAwIjC5TgLffO4BYrM0yJOhTX8j21t3s=; b=TP4SQDgrUarcDZVB45ZDkj0SVp3qxMpUQ6qeNgswORyQaiKyI4o+YPu10KCiE3vkW3 CZ886bFgp6vvXj5uKXJmoxWnl0WX2+bAU4bNJaD/cF7dvldBxjVQb4ni5Oa6bsmCdd7C i0+CF7prMRJA3fjwONNi/w5iyDTQC9GMSj1kdRdz7qE8z1dugYa6PbSa41GCcj29SL3l LztGmt4xjl2vgrM+oLWlPXES/3uN5cCMx9MRzYbBqE6DPfG/Cp/caa2g8eRFfGtgpv7X 8IGDZb03hWLqNFr+mVMVveW1RWR5KBDtK05SQgiKPzK2x+/IMKU1uG4EmiCYlJblX5LG eZqA== MIME-Version: 1.0 Received: by 10.224.107.5 with SMTP id z5mr52418342qao.48.1357754131544; Wed, 09 Jan 2013 09:55:31 -0800 (PST) Received: by 10.49.35.204 with HTTP; Wed, 9 Jan 2013 09:55:31 -0800 (PST) In-Reply-To: References: Date: Wed, 9 Jan 2013 17:55:31 +0000 Message-ID: Subject: Re: Web Console: Empty Message Details (but message is fine in stomp) From: James Green To: users Content-Type: multipart/alternative; boundary=20cf3074afd2b3fa7504d2dec42d X-Virus-Checked: Checked by ClamAV on apache.org --20cf3074afd2b3fa7504d2dec42d Content-Type: text/plain; charset=ISO-8859-1 I've only tried on this one test server but all the data I'm throwing in ends up empty in the console but fully-formed in a stomp client. Interestingly if I consume the "bad message" and forward it onward it remains unreadable in the console. This is occurring across a number of messages including process paths long considered reliable in the past. So it seems to be something perhaps recently changed? On 9 January 2013 16:43, Dejan Bosanac wrote: > Hi James, > > it doesn't sound familiar. Any chance you can reproduce it? > > > Regards > -- > Dejan Bosanac > ---------------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > dbosanac@redhat.com > Twitter: @dejanb > Blog: http://sensatic.net > ActiveMQ in Action: http://www.manning.com/snyder/ > > > On Wed, Jan 9, 2013 at 10:28 AM, James Green > wrote: > > Got a weird one. We have a series of queues and just in the past day or > two > > I've realised that some of the queues are reporting blank message details > > in the web console. > > > > Here's the page source: > >
> > > > Yet for another queue, holding different XML data: > >
<?xml
> > version="1.0"?><Event><VoiceCollection
> > CallId="398" MessageId="92"
> > AccountId="200000"
> >
> Hash="27fbd117057f3e983b172d31ddd4465d"Cost="0"/></Event>
> > > > The one that appears blank in the console has the following body when > read > > using stomp: > > > > Portal2013-01-08 > > 17:50:40SENT{"CollectedAt":"2013-01-07 > > > 15:15:00","ReceiptAt":"2013-01-08T17:50:40+00:00"}2703ef951-203a-4a23-998d-3ede8e654900703ef951-203a-4a23-998d-3ede8e654900 > > > > Any ideas what might be causing such a thing to occur? > > > > Broker version: 5.7.0. > > > > Thanks, > > > > James > --20cf3074afd2b3fa7504d2dec42d--