You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Joel Turkel (Created) (JIRA)" <ji...@apache.org> on 2011/10/20 15:52:10 UTC

[jira] [Created] (CXF-3867) Fix for CXF-1816 causes startup performance regression

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.4, 2.3, 2.2
            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

        

[jira] [Updated] (CXF-3867) Fix for CXF-1816 causes startup performance regression

Posted by "Joel Turkel (Updated) (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Resolved] (CXF-3867) Fix for CXF-1816 causes startup performance regression

Posted by "Daniel Kulp (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-3867.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.1
                   2.4.5
                   2.3.8
         Assignee: Daniel Kulp


Added a system property (org.apache.cxf.JDKBugHacks.defaultUsesCaches) and a META-INF/cxf file that can be used to control it.
                
> 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
>            Assignee: Daniel Kulp
>             Fix For: 2.3.8, 2.4.5, 2.5.1
>
>
> 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

        

[jira] [Commented] (CXF-3867) Fix for CXF-1816 causes startup performance regression

Posted by "Joel Turkel (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178583#comment-13178583 ] 

Joel Turkel commented on CXF-3867:
----------------------------------

It looks like the approach of using a META-INF/cxf/org.apache.cxf.JDKBugHacks.defaultUsesCaches file to configure this feature requires the resource to be in the system classloader (because the first line of JDKBugHacks.doHacks() sets the current thread context classloader to the system classloader). Is this expected? It makes it harder to deploy the workaround in certain environments.
                
> 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
>            Assignee: Daniel Kulp
>             Fix For: 2.3.8, 2.4.5, 2.5.1
>
>
> 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