[
https://issues.apache.org/jira/browse/AMQ-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690446#comment-13690446
]
Ryan Stewart commented on AMQ-2920:
-----------------------------------
This issue isn't actually resolved. My 5.8.0 broker was failing to start
because of a NullPointerException (my fault in the configuration), and the
error didn't appear until I changed the ">/dev/null" to
">/opt/activemq/data/activemq.out".
> new ActiveMQ 5.4.0 sysv start script redirects process stdout and stderr to
> /dev/null
> -------------------------------------------------------------------------------------
>
> Key: AMQ-2920
> URL: https://issues.apache.org/jira/browse/AMQ-2920
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0
> Reporter: Mats Henrikson
> Assignee: Gary Tully
> Fix For: 5.6.0
>
>
> It appears that the new sysV start/init script redirects all the process
> output to /dev/null when starting the broker.
> This leads to pain and confusion, since you will not see any error output
> when you have e.g. a non-compliant activemq.xml config file - the script just
> completes successfully but your broker has not started. To see the output you
> actually have to hack the init script to remove the /dev/null, or get the
> script to output the command line so that you can run it by hand to get the
> error output.
> The process output should probably be redirected to some log file in the data
> directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
