Return-Path: 
 <users-return-33169-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
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 192A1E51C
	for <apmail-activemq-users-archive@www.apache.org>;
 Wed,  9 Jan 2013 09:28:57 +0000 (UTC)
Received: (qmail 93089 invoked by uid 500); 9 Jan 2013 09:28:56 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 92836 invoked by uid 500); 9 Jan 2013 09:28:56 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 92802 invoked by uid 99); 9 Jan 2013 09:28:55 -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 09:28:55 +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.51 as permitted sender)
Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 09:28:47 +0000
Received: by mail-qa0-f51.google.com with SMTP id i20so525293qad.17
        for <users@activemq.apache.org>; Wed, 09 Jan 2013 01:28:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=u098vcZcxa7mypLEutleTUK1Ut9CseWaL7+SUWgxnK8=;
        b=BnJRFj/Nl7XpukxLMblr/J1DDyHSFzqixYQemnmkkmEvEgmhiw22xXVk0Q/6fmz+OS
         zuuBZGlx49mkqcSm9Gk9JvhbXYX3EU9hyC9m+nuvWU29sqWjExpryj1US5hwjMYCt7X+
         02eQFylky7K6zsY9gPxU1ltpEyBwHNqBM6bRzCNg4AFubSI9S3IdoQ+VkmnFbgY84i5h
         DlV9IpVBhYfghiY6c8z8IwuAN/vYOA5p25iokRan1F9tXZRHPqXvrDHV7KMv0SwD1mBk
         KTl8ram3r0IpBslccgDSn3JkglaIlOQ8O1pwh0+uea6c4RrDxgxAa1ZmBvvC8buN+a4w
         i7fw==
MIME-Version: 1.0
Received: by 10.224.58.69 with SMTP id f5mr24627698qah.87.1357723706639; Wed,
 09 Jan 2013 01:28:26 -0800 (PST)
Received: by 10.49.35.204 with HTTP; Wed, 9 Jan 2013 01:28:26 -0800 (PST)
Date: Wed, 9 Jan 2013 09:28:26 +0000
Message-ID: 
 <CAMH6+ayH=kJY3f=UWfg_FP8b0PSAJrnsWHAONq93V+AnW7mevw@mail.gmail.com>
Subject: Web Console: Empty Message Details (but message is fine in stomp)
From: James Green <james.mk.green@gmail.com>
To: users <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=20cf3074b4783cc37404d2d7aff7
X-Virus-Checked: Checked by ClamAV on apache.org

--20cf3074b4783cc37404d2d7aff7
Content-Type: text/plain; charset=ISO-8859-1

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:
<div class="message"><pre class="prettyprint"></pre></div>

Yet for another queue, holding different XML data:
<div class="message"><pre class="prettyprint">&lt;?xml
version=&#034;1.0&#034;?&gt;&lt;Event&gt;&lt;VoiceCollection
CallId=&#034;398&#034; MessageId=&#034;92&#034;
AccountId=&#034;200000&#034;
Hash=&#034;27fbd117057f3e983b172d31ddd4465d&#034;Cost=&#034;0&#034;/&gt;&lt;/Event&gt;</pre></div>

The one that appears blank in the console has the following body when read
using stomp:
<?xml version="1.0"?>
<notification><source>Portal</source><datetime>2013-01-08
17:50:40</datetime><state>SENT</state><reason>{"CollectedAt":"2013-01-07
15:15:00","ReceiptAt":"2013-01-08T17:50:40+00:00"}</reason><account>2</account><tag>703ef951-203a-4a23-998d-3ede8e654900</tag><remoteId>703ef951-203a-4a23-998d-3ede8e654900</remoteId></notification>

Any ideas what might be causing such a thing to occur?

Broker version: 5.7.0.

Thanks,

James

--20cf3074b4783cc37404d2d7aff7--