-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
JBoss A-MQ 6.0, JBoss A-MQ 6.2, JBoss A-MQ 6.2.1
-
None
When trace=true is enabled on the openwire transport connector in the broker/activemq.xml,
each time clients connect to the broker new instances of TransportLogger, org.apache.log4j.CategoryKey, org.slf4j.impl.Log4jLoggerAdapter, org.apache.log4j.Logger are created and added to the HashTable in the org.apache.log4j.Hierarchy singleton. They don't get evicted after the clients disconnect or upon GC events, leading to eventual (or more rapid in environments with a lot of connection churn) heap growth until heap is consumed.
- is related to
-
ENTMQ-1203 New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true
- Closed
- relates to
-
ENTMQ-1203 New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true
- Closed