[
https://issues.apache.org/jira/browse/AMQ-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976282#comment-16976282
]
ASF subversion and git services commented on AMQ-6963:
------------------------------------------------------
Commit fd61bb62bd8423b37938a8e70f4e46c332511f0d in activemq's branch
refs/heads/activemq-5.15.x from saivr1t
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=fd61bb6 ]
AMQ-6963 Fix calling the toString() method in case of different log level.
(cherry picked from commit 191e4ffbe6ce863980f6d239c49589055dd5535b)
> 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)
