e.org/message-cursors.html
Here you can find destinatons policies parameters and their default values:
http://activemq.apache.org/per-destination-policies.html
--
View this message in context:
http://activemq.2283324.n4.nabble.com/QueueBrowser-does-not-return-large-messages-tp4656447p4659112.html
I got this solved now. It was a problem with the per-destination policy.
Adding
to the config made it work.
Best regards,
Andr
On Fri, Sep 21, 2012 at 3:37 PM, Andreas Maza wrote:
> Thanks for your response. I am wondering that nobody ran in such an issue
> so far. No, there is no truncatio
Thanks for your response. I am wondering that nobody ran in such an issue
so far. No, there is no truncation - neither in the web console nor in my
own implementation.
So your suggestions is to browse/view the messages via JMX using an
appropriate destination policy? is this already possible now o
I would expect some sort of truncation on the body of a large message
for the UI. So show only a few 100 bytes. sort of thing.
Like we do when we log a message.
If you use jconsole, do you see the full 20MB?
To implement browsing limited to headers, that would require some code
changes to suppor
Hi folks,
I am facing a problem when accessing my messages (in the DLQ) with the
queue browser: it works for "regularly-sized" messages, but it does not
return anything for large messages. I have 4 messages in my queue, where
three of them are about 20MB each. I use the ActiveMQ queue browser
imp
