JournalInactive messages appear when certain broker scheduling algorithms are triggered and the user is running at INFO log level. There is nothing a customer can do to stop the scheduling triggers and there is no convenient way to turn the JournalInactive messages off.
The user log file is filled with repetitive JournalInactive messages.
The priority of the JournalInactive log messages is lowered to DEBUG level and the message frequency is lowered from 12/second to 1/second. If the broker is running at INFO log level the JournalInactive messages may be selectively re-enabled by using switch: --log-enable debug+:Timer
The users log file is not cluttered with JournalInactive messages.