This bug is a result of bug 620742.
The store will change some of its configuration parameters (see 6.3. Configuring the Journal - http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/html/Messaging_User_Guide/sect-Messaging_User_Guide-Persistence-Configuring_the_Journal.html) to legal values if the supplied values are out of range. This behaviour is not consistent with that of the broker, and there should be some warning about this in the store documentation.
I suggest the following (please feel free to adapt, other suggestions welcome):
1. Place an info or note style box below table 6.1 with the heading "Auto-correcting parameters" and the following text:
Note that if an out-of-range or illegal parameter is supplied to the store, it will automatically replace it with the closest legal value and place a warning in the log file rather than fail. This applies to all numeric parameters, ie num-jfiles, jfile-size-pgs, wcache-page-size, tpl-num-jfiles, tpl-jfile-size-pgs and tpl-wcache-page-size.
For example, starting the store with --num-jfiles 1 (which is out-of-range, the minimum allowed is 4), the store will automatically substitute a value of 4 and place the following warning into the log file: "warning parameter num-jfiles (1) is below allowable minimum (4); changing this parameter to minimum value."
Similarly, if a value which is not a power of 2 is given the for wcache-page-size parameter, the closest power of 2 will be substituted with a warning in the log file.
2. Add the following sentence to each of the affected parameters (ie all of them in table 6.1 except the first one):
"See the notice "Auto-correcting Parameters" below, which applies to this parameter."
Fixed in checked-in doc source, will show in next build.
Closed as fix already implemented