You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2018/03/16 19:40:00 UTC

[jira] [Closed] (AMQ-6930) bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode

     [ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-6930.
-----------------------------
    Resolution: Not A Problem

This is intentional and shouldn't be changed, if you want to debug you should use the console option to run in the foreground or view the broker logs when running as a daemon.

> bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode
> ---------------------------------------------------------------------------
>
>                 Key: AMQ-6930
>                 URL: https://issues.apache.org/jira/browse/AMQ-6930
>             Project: ActiveMQ
>          Issue Type: Wish
>    Affects Versions: 5.15.0, 5.15.1, 5.15.2, 5.15.3
>            Reporter: Alvin Lin
>            Priority: Major
>
> if I do "bin/activemq start" the ActiveMQ process is started with stdout/stdin redirected to /dev/null. 
> This makes it hard to debug issue like out of memory error because we can't see any log, for example, when the JVM flag "ExitOnOutOfMemoryError" is turned on. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)