maxTotalMsgBytes not propogating correctly through cluster

I'm trying to set the maxTotalMsgBytes to 500 Mb for a destination (queue). I'm running a 2 broker cluster (3.5 SP1). On one of the servers, I enter -o maxTotalMsgBytes=524288000

as a parameter for an imqcmd update dst

or imqcmd create dst

command. When I query the destination after, the property has been set as expected:

Max Total Message Bytes524288000

However, on the other broker in the cluster, it has been multiplied by 1024:

Max Total Message Bytes536870912000

If I then try to update the other broker, the reverse happens. I can't seem to get them to be the same, and only the correct broker is honouring my limitBehavior when the limit is reached.

Anyone have a work around for this?

[762 byte] By [aeddydev] at [2007-11-25 17:03:41]