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 <[email protected]> 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 > [email protected] > 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 <[email protected]> > 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: > > <div class="message"><pre class="prettyprint"></pre></div> > > > > Yet for another queue, holding different XML data: > > <div class="message"><pre class="prettyprint"><?xml > > version="1.0"?><Event><VoiceCollection > > CallId="398" MessageId="92" > > AccountId="200000" > > > Hash="27fbd117057f3e983b172d31ddd4465d"Cost="0"/></Event></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 >
