activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-6930) bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode
Date Fri, 16 Mar 2018 19:40:00 GMT

     [ 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)

Mime
View raw message