activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4721) Update slf4j library to latest version (1.7.5 currently)
Date Thu, 12 Sep 2013 17:30:52 GMT

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

Timothy Bish commented on AMQ-4721:
-----------------------------------

So far it looks good, lot of changes to review.  One thing we might want to do is split the
versions configure different slf4j api and impl versions like camel does.  
                
> Update slf4j library to latest version (1.7.5 currently)
> --------------------------------------------------------
>
>                 Key: AMQ-4721
>                 URL: https://issues.apache.org/jira/browse/AMQ-4721
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.8.0
>            Reporter: Timothy Bish
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: 5.9.0
>
>         Attachments: AMQ-4721.patch
>
>
> We are currently on an older release v1.6.6 and should move on to the latest v1.7.5 to
pick up performance improvements etc.  
> From the changelog:
> "performance improvements: The logger factories in most SLF4J modules namely in jcl-over-slf4j,
log4j-over-slf4j, slf4j-jcl, slf4j-jdk14, slf4j-log4j12, and slf4j-simple now use a ConcurrentHashMap
instead of a regular HashMap to cache logger instances. This change significantly improves
logger retrieval times at the cost of some memory overhead. This improvement was requested
in bug #298 by Taras Tielkes who also provided the relevant patch. 
> Given the significance of these performance improvements, users are highly encouraged
to migrate to SLF4J version 1.7.5 or later. "

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message