[
https://issues.apache.org/jira/browse/DISPATCH-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243678#comment-14243678
]
ASF subversion and git services commented on DISPATCH-85:
---------------------------------------------------------
Commit 1644825 from [~aconway] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1644825 ]
DISPATCH-85: Remove all direct printing to stdout and stderr.
The only thing qdrouterd was printing to stderr was the debugging information
about final status of allocators. This can't be logged normally because the
logging system is already finalized at that point.
Solution: a new container configuration attribute debugDump. If set to a file
name, allocator info is written to that file during shutdown.
> Remove all direct printing to stdout and stderr.
> ------------------------------------------------
>
> Key: DISPATCH-85
> URL: https://issues.apache.org/jira/browse/DISPATCH-85
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 0.2
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Trivial
> Fix For: 0.3
>
>
> A running dispatch router should never print directly to stdout/stderr, in
> daemon mode they are piped to /dev/null. All errors, warnings etc. should be
> sent through the logging system (which can of course be configured to log to
> stdout/stderr). Only command-line startup issues that prevent qdrouterd from
> starting should go direct stdout/stderr.
> There are not many of these left, most are from the proton library, I'll
> raise a separate bug for that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
