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

Alvin Lin commented on AMQ-6930:
--------------------------------

There is actually one more thing regarding this change. We may need to add 
documentation on the things to be aware of when setting ACTIVEMQ_OUT. 

Since ActiveMQ by default configures a console appender for log, so when an 
user configures ACTIVEMQ_OUT all the logs logged to activemq.log will also be 
logged to $ACTIVEMQ_OUT. So maybe we want to document this and mention about 
they can disable the ConsoleAppender in log4j.properties; also, the document 
should probably mention about using logrotate to rotate $ACTIVEMQ_OUT and that 
logrotate should use "copy truncate". 

I am more than happy to contribute to the documentation if I can get some lead 
on the source of the ActiveMQ website and the documentation release process; we 
definitely don't want to expose the documentation for ACTIVEMQ_OUT before it's 
release :)

> 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
>             Fix For: 5.16.0, 5.15.4
>
>
> 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)

Reply via email to