cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessio Soldano (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CXF-6738) Reduce contention on org.apache.cxf.binding.soap.SoapTransportFactory$SoapEndpointInfo
Date Thu, 07 Jan 2016 21:47:39 GMT
Alessio Soldano created CXF-6738:
------------------------------------

             Summary: Reduce contention on org.apache.cxf.binding.soap.SoapTransportFactory$SoapEndpointInfo
                 Key: CXF-6738
                 URL: https://issues.apache.org/jira/browse/CXF-6738
             Project: CXF
          Issue Type: Improvement
          Components: JAX-WS Runtime
            Reporter: Alessio Soldano


By profiling some benchmark application, org.apache.cxf.binding.soap.SoapTransportFactory$SoapEndpointInfo
has been found in the contention hotspots. That's because of the multiple synchronized blocks
in org.apache.cxf.ws.policy.PolicyEngineImpl, which seem to be there basically for lazily
getting the effective policy once the endpoint is fully initialized.
I propose to replace those synchronized blocks with (properly implemented) double-checked
locking idiom so that no locking actually happens after endpoints have been initialized.



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

Mime
View raw message