You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Mike Bonnet (JIRA)" <ji...@apache.org> on 2016/11/21 22:47:59 UTC

[jira] [Commented] (PROTON-1347) Container prints to stderr on connection timed out

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

Mike Bonnet commented on PROTON-1347:
-------------------------------------

Looks like this is the line that's responsible:

https://github.com/apache/qpid-proton/blob/master/proton-c/bindings/python/proton/handlers.py#L404

So I can avoid the print by overriding that method or reconfiguring the logger. This could be considered not a bug, so if you want to close this JIRA, go ahead. However, logging could be handled a little better, rather than sending all messages to the root logger.

> Container prints to stderr on connection timed out
> --------------------------------------------------
>
>                 Key: PROTON-1347
>                 URL: https://issues.apache.org/jira/browse/PROTON-1347
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: python-binding
>    Affects Versions: 0.14.0
>            Reporter: Mike Bonnet
>            Assignee: Justin Ross
>            Priority: Minor
>
> If you're using a Container to connect to a broker, and the broker is unresponsive and the connection times out, this is printed to stderr:
> ERROR:root:proton:io: recv: Connection timed out
> Libraries generally shouldn't print directly to the console, especially when the error can be handled in the code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org