Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7609

Cache getResources in all layers (backport JBCL-181)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.1
    • None
    • None
    • Release Notes
    • Hide
      Classloading classes did not cache the results of getResourcesLocally(), as they do for getResourceLocally(), resulting in Classloader.getResources() running slowly. This could cause performance issues if it was called often, as Java's ServerFinder would do if its results were not cached. To resolve this issue, caching has now been implemented in classloading classes, resulting in better overall performance.
      Show
      Classloading classes did not cache the results of getResourcesLocally(), as they do for getResourceLocally(), resulting in Classloader.getResources() running slowly. This could cause performance issues if it was called often, as Java's ServerFinder would do if its results were not cached. To resolve this issue, caching has now been implemented in classloading classes, resulting in better overall performance.
    • Documented as Resolved Issue
    • NEW

      BaseClassloader's getResources() and getResourcesLocally() methods perform slowly compared to getResource()/getResourceLocally(). This is because getRescourceLocally() implements a cache that it checks first to quickly return repeated resources while getResourcesLocally() implements no cache but goes straight to the VFS. The fix implement similar caching for getResourcesLocally().

              Unassigned Unassigned
              rhn-support-jlivings James Livingston (Inactive)
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: