[embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-360) JarURLConnection default cache disabled globally

[Ian Springer (JIRA)]

    [ https://issues.jboss.org/browse/EMBJOPR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617355#comment-12617355 ] 

Ian Springer commented on EMBJOPR-360:
--------------------------------------

A potential workaround would be for the app that wants to enable URL caching to invoke:

someUrlConnection.setDefaultUseCaches(true)

thus resetting the default back to true. My only concern would be that something in Facelets might break if it relies on URL caching being disabled.

Jason, any chance you could try the following and see what happens?

1) start up EAP.
2) login to the admin-console and wait for it to fully init.
3) hit some other app that invokes setDefaultUseCaches(true).
4) go back to the admin-console and surf around a bit and make sure everything is still working.



> JarURLConnection default cache disabled globally
> ------------------------------------------------
>
>                 Key: EMBJOPR-360
>                 URL: https://issues.jboss.org/browse/EMBJOPR-360
>             Project: Embedded Jopr
>          Issue Type: Bug
>          Components: Core Infrastructure
>    Affects Versions: 1.3.4
>         Environment: JBoss Enterprise Application Platform (EAP) 5.1
> Embedded Jopr 1.3.4.SP1
>            Reporter: Jason Shepherd
>              Labels: classloading, jar
>         Attachments: URLConnectionCache.war, URLConnectionCache.zip
>
>
> The admin-console in EAP 5.1 is turning off caching of resources contained within jars globally. This is causing a serious performance impact in using standard java functions, such as creating DocumentBuilderFactory instances.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira