[
https://issues.apache.org/jira/browse/AMQ-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Savonin updated AMQ-6963:
-----------------------------------
Description:
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
was:
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)
> 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
> Priority: Minor
> Fix For: 5.16.0
>
>
> 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
(v7.6.3#76005)
