Hiram Chirino wrote:
By default we use 2 x 20 meg journal files.
The logs need to hold a good working set of the in flight persistent
messages that are flowing through the system. It's optimum if message
that was written to the log file is held long enough so that ack for
that message can be written to the log file (basically before we
checkpoint the message to the jdbc store). that allows us to avoid
moving most of the messages that are flowing through the system to jdbc
which is quite slow by comparison.
And since activemq supports moving allot of msg/sec and the message can
be quite large, 2 x 20 meg log files is a quite conservative setting.
Now if your not using JMS at all, I would guess that's too much!
Any chance of changing this behavior such that the the 40M growth is
only incurred when JMS is actually being used (i.e. lazy creation of the
logs based on the first JMS use)?
