[
https://issues.apache.org/jira/browse/CXF-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119188#comment-15119188
]
ASF GitHub Bot commented on CXF-6738:
-------------------------------------
Github user asoldano commented on the pull request:
https://github.com/apache/cxf/pull/105#issuecomment-175604073
I've applied the changes directly, closing the PR.
> 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)
