You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2016/09/30 15:58:20 UTC
[jira] [Updated] (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:all-tabpanel ]
Gary Tully updated AMQ-6446:
----------------------------
Description:
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.
was:
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
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)