The problem you are facing appears beacuse of standard, store based cursors
that works very well when consumers are reading from the queue.
In a few words when message comes to a queue it is persisted in a store and
passed to a dispatch queue from which it is read by consumer. When consumer
is
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
