You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/09/30 13:06:20 UTC

[jira] [Commented] (AMQ-6446) New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true

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

ASF subversion and git services commented on AMQ-6446:
------------------------------------------------------

Commit 5385fd1bb36abe5a123db039b63d30cefd594ba4 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5385fd1 ]

https://issues.apache.org/jira/browse/AMQ-6446 - use shared logger and pepend statements with connection counter. Old behaviour or per connection logger can be obtained with trace=true&jmxPort=0


> New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6446
>                 URL: https://issues.apache.org/jira/browse/AMQ-6446
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 5.15.0
>
>
> Configuring the broker for transport trace:|{code}<transportConnectorname="openwire"uri="tcp://0.0.0.0:61616?trace=true"/>
> </transportConnectors>{code}
> makes the broker create a new SLF4J Logger instance for every single connection.
> This Logger never get cleared not even when the connection is closed which can lead to OOM on load.
> trace=true is a great diagnostic tool but cannot be left enabled on a broker long term because of this.
> If possible using a logger per transport connector would be better



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