activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2920) new ActiveMQ 5.4.0 sysv start script redirects process stdout and stderr to /dev/null
Date Thu, 16 Sep 2010 08:40:41 GMT

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

Gary Tully commented on AMQ-2920:
---------------------------------

does using the console mode, "./bin/activemq console"  help here?

> new ActiveMQ 5.4.0 sysv start script redirects process stdout and stderr to /dev/null
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-2920
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2920
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.0
>            Reporter: Mats Henrikson
>
> It appears that the new sysV start/init script redirects all the process output to /dev/null
when starting the broker.
> This leads to pain and confusion, since you will not see any error output when you have
e.g. a non-compliant activemq.xml config file - the script just completes successfully but
your broker has not started. To see the output you actually have to hack the init script to
remove the /dev/null, or get the script to output the command line so that you can run it
by hand to get the error output.
> The process output should probably be redirected to some log file in the data directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message