Syntax errors are not showing up in the log when the broker is started in the
background
-----------------------------------------------------------------------------------------
Key: AMQ-3747
URL: https://issues.apache.org/jira/browse/AMQ-3747
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.5.1
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.6.0
*Issue:*
When there is a simple syntax error in the configuration file, e.g.:{code}
<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>{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
