[
https://issues.apache.org/jira/browse/PROTON-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404680#comment-16404680
]
Robbie Gemmell commented on PROTON-1797:
I disagree. The logging is not actually about an error, so I don't see
particular reason that it would belong on stderr more than it does stdout. I
expect thats probably why it uses stdout. I didn't write it originally, but I
would pick stdout today if I was doing so (or as likely, use a logging
framework). I don't think 'something else users stderr' is a reason to change
it after several years in any event.
> Transport log is written on stdOut instead of stdErr
>
>
> Key: PROTON-1797
> URL: https://issues.apache.org/jira/browse/PROTON-1797
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
>Affects Versions: proton-j-0.24.0
>Reporter: David Kornel
>Priority: Minor
>
> When I export PN_TRACE_FRM=1 client writes frames on stdOut instead of stdErr
> like in proton-python client.
>
> https://github.com/apache/qpid-proton-j/blob/e7aae9469ac2f45a6de1822d7fe3cd2d4c8a314c/proton-j/src/main/java/org/apache/qpid/proton/engine/impl/TransportImpl.java#L1694-L1709
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
