You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2019/11/18 04:51:00 UTC
[jira] [Assigned] (AMQ-6963) ActiveMQConnection: fix logging for
avoid volatile read in case of different loglevel
[ https://issues.apache.org/jira/browse/AMQ-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned AMQ-6963:
-----------------------------------------
Assignee: Jean-Baptiste Onofré
> 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
> Reporter: Alexander Savonin
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 5.16.0, 5.15.11
>
>
> 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)