cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-7184) Double checked locking in PolicyEngineImpl.java
Date Thu, 22 Dec 2016 13:23:58 GMT

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

Daniel Kulp resolved CXF-7184.
------------------------------
       Resolution: Not A Bug
         Assignee: Daniel Kulp
    Fix Version/s: Invalid

There isn't any locking at all in the createEndpointPolicyInfo method.    There is no assignment
to any instant variables.

> Double checked locking in PolicyEngineImpl.java
> -----------------------------------------------
>
>                 Key: CXF-7184
>                 URL: https://issues.apache.org/jira/browse/CXF-7184
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 3.2.0, 3.1.8, 3.1.10, 3.0.13
>            Reporter: Wil Evers
>            Assignee: Daniel Kulp
>             Fix For: Invalid
>
>
> Method createEndpointPolicyInfo() in rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/PolicyEngineImpl.java
contains a classic instance of the double checked locking pattern, which may cause an object
to become visible to a different thread in a partially initialized state.
> Please see The "Double-Checked Locking is Broken" Declaration (https://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html)
to understand why this happens. A quick Google search should return several possible solutions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message