[ 
https://issues.apache.org/jira/browse/AMQ-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved AMQ-6963.
---------------------------------------
    Resolution: Fixed

> ActiveMQConnection: fix logging for avoid volatile read in case of different 
> loglevel
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-6963
>                 URL: https://issues.apache.org/jira/browse/AMQ-6963
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client
>            Reporter: Alexander Savonin
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: 5.16.0, 5.15.11
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Just a little improvement for ActiveMQConnection to preventing of call the 
> 'toString()' method in case of different log level, because toString() could 
> create additional objects or could read volatile variable. For example:
>  org.apache.activemq.ActiveMQConnection#toString (AtomicBoolean)
> PR: https://github.com/apache/activemq/pull/283



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to