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 or does this need some code changes anyway? In JConsole, when doing a browse() all messages are returned. Some of them (I guess the smaller ones) contain a bodyPreview field (with a byte[255] since I am transferring byte[]) and some messages do not contain the bodyPreview field. Best regards, Andr On Tue, Sep 18, 2012 at 12:26 PM, Gary Tully <gary.tu...@gmail.com> wrote: > I would expect some sort of truncation on the body of a large message > for the UI. So show only a few 100 bytes. <abc...xyz> 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 support it. I think simplest would be a broker side > destination policy that limits a browse to headers only. > > There would be more work to add it as a consumer option, or maybe hack > it into the selector in some way. > > In any event, please raise an enhancement request, this is worth some > more thought and it would be easy/low impact to work in the > destination policy. > > On 14 September 2012 07:29, Andreas Maza <andr.m...@gmail.com> wrote: > > 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 > > implementation in my admin GUI - it shows a queue size of 4, but when I > > want to browse the queue, nothing is returned and I also do not receive > any > > exceptions. The same behaviour applies for the ActiveMQ web console > (which > > runs on the same host as the ActiveMQ instance). > > > > In general, I would prefer to load only the JMS headers when browsing a > > queue for efficieny reasons. Any hints how this can be done using the > queue > > browse or how to avoid the above mentioned behavior? > > > > Thanks and best regards, > > > > > > Andr > > > > -- > http://fusesource.com > http://blog.garytully.com >
