activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-6930) bin/activemq should allow stdout/stderr to some file instead of /dev/null for daemon mode
Date Tue, 10 Apr 2018 18:41:00 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432748#comment-16432748
] 

Jamie goodyear edited comment on AMQ-6930 at 4/10/18 6:40 PM:
--------------------------------------------------------------

Given the new behavior is controlled via environment variable switch, I think this is a fare
change to make.

Classic behavior is retained unless you need the optional output location set.


was (Author: jgoodyear):
Given the new behavior is controlled via environment variable switch, I think this is a fare
change to make.

> bin/activemq should allow stdout/stderr to some file instead of /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