[
https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432697#comment-16432697
]
ASF GitHub Bot commented on AMQ-6930:
-------------------------------------
GitHub user alvinlin123 opened a pull request:
https://github.com/apache/activemq/pull/281
AMQ-6930 Expose an environment variable to allow redirect stdout/stderr to
a file
This change does not modify the default behavior, the default behavior is
still to pipe stdout/stderr to /dev/null. User can specify a file using an
environment variable called `ACTIVEMQ_OUT` to redirect stdout/stderr to the
file.
This change also added and fixed some tests in
`assembly/src/test/scripts/init-script-testsuite`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alvinlin123/activemq amq-6930
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/281.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #281
----
commit f3a8e882068803a3cdab338d3544b27a7808e0cc
Author: Alvin Lin <alvinlin@...>
Date: 2018-04-09T23:53:44Z
AMQ-6930 provide options to allow stdout/stderr of activemq process to be
redirect to a file using append mode
commit 6bb56decf881328f5595692ca17c1899f7f86a7b
Author: Alvin Lin <alvinlin@...>
Date: 2018-04-10T02:04:55Z
AMQ-6930 add test case
----
> 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)
