The real issue to me is how much space the message uses in the heap. That size value is important because it is used to help prevent out of memory errors. The usage calculations are based off of it so you don't want to underestimate the message size in memory.
One thing you could do would be to take a heap dump of your messages in memory and see exactly how much space they are using up if you want to try and set the size to a more accurate value. That being said, I wouldn't really be too concerned with that size value since again it's just an estimation and used for things like usage tracking. Changing the minimum size that the method reports isn't going to change how much space the actual message is using in memory or on disk. On Tue, Feb 23, 2016 at 4:08 PM, kal2 <kinfo0...@gmail.com> wrote: > any idea how changing the value to something lower will impact the > broker? I > expect the size of the msg payload to be between 400bytes to 1kb? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/why-MSG-size-in-activemq-is-much-larger-than-payload-tp4708070p4708155.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
