[AMQ-3747] Syntax errors are not showing up in the log when the broker is started in the background

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.1
• Fix Version/s: 5.6.0
• Component/s: Broker
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 29/Feb/12 14:38
• Updated: 29/Feb/12 14:46
• Resolved: 29/Feb/12 14:46

Description

Issue:
When there is a simple syntax error in the configuration file, e.g.:

<policyEntry queue="MY.INPUTQ" producerFlowControl="true" memoryLimit="50mb">
           <pendingQueuePolicy>
                 <vmQueueCursor/>
           </pendingQueuePolicy>
</policyEntry>
           <pendingQueuePolicy>     <=== This is incorrect as it isn't associated with policy entry
                  <vmQueueCursor/>
           </pendingQueuePolicy>
                </policyEntry>

When I start the broker in the foreground, broker console, I see loads of SAX parser errors. None of these are in the log. If I start the broker in the background, broker start, nothing shows up in the log. Can we fix this up so syntax errors go to the log?

Problem:
The background start script redirects to dev/null so console output is lost intentionally. Otherwise the default console logging would fill up system logs.
However there is no other indication of a parse error of the xml configuration apart from the exception printed to the console.

Solution:
The error should also go to the default log so it needs to be trapped at source and logged there before being propagated back to the command line caller.

Issue Links

• is duplicated by: AMQ-2920 new ActiveMQ 5.4.0 sysv start script redirects process stdout and stderr to /dev/null