You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2018/03/19 11:19:00 UTC
[jira] [Closed] (PROTON-1797) Transport log is written on stdOut
instead of stdErr
[ https://issues.apache.org/jira/browse/PROTON-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell closed PROTON-1797.
----------------------------------
Resolution: Not A Problem
This isn't a bug. I didn't write it, but the choice now I'd probably also think stdout is preferable to stderr personally. That the two differ is perhaps odd, but its definitely not a bug in proton-j.
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org