cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Turkel (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-3867) Fix for CXF-1816 causes startup performance regression
Date Thu, 20 Oct 2011 13:54:10 GMT

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

Joel Turkel updated CXF-3867:
-----------------------------


Note it's possible to workaround this by resetting the default value for connection caching
e.g.

{code}
// Grab a logger from CXF to force CXF to install its workarounds
LogUtils.getL7dLogger(getClass());

// Create a dummy URL connection so we can change the default value
URLConnection urlConnection = new URLConnection(new URL("jar:file://dummy.jar!/")) {
	
	@Override
	public void connect() throws IOException {
		// Do nothing
	}
};
urlConnection.setDefaultUseCaches(true);
{code}
                
> Fix for CXF-1816 causes startup performance regression
> ------------------------------------------------------
>
>                 Key: CXF-3867
>                 URL: https://issues.apache.org/jira/browse/CXF-3867
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.2, 2.3, 2.4
>            Reporter: Joel Turkel
>
> The fix for CXF-1816 is causing a 50% startup performance regression for my application.
The problem stems from changing the default value for URL connection caching to false which
really slows down classloader performance. Perhaps CXF could make this workaround configurable
like Tomcat does with the urlCacheProtection setting?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message