Bad performance loading resources from JBoss jars after Facelets-using application starts

Solution Unverified - Updated -

Issue

  • We had experimented a big performance issue after the admin-console started for the first time in JBoss 5.1 EAP.
  • We are seeing bad performance, and profiling shows that a substantial amount of time is spent verifying the signatures on JBoss jars:
  at java.util.HashMap.createEntry(HashMap.java:901)
  at java.util.HashMap.addEntry(HashMap.java:888)
  at java.util.HashMap.put(HashMap.java:509)
  at java.util.jar.Attributes.put(Attributes.java:148)
  at java.util.jar.Attributes.putValue(Attributes.java:168)
  at java.util.jar.Attributes.read(Attributes.java:421)
  at java.util.jar.Manifest.read(Manifest.java:251)
  at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:206)
  at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:193)
  at java.util.jar.JarVerifier.processEntry(JarVerifier.java:305)
  at java.util.jar.JarVerifier.update(JarVerifier.java:216)
  at java.util.jar.JarFile.initializeVerifier(JarFile.java:345)
  at java.util.jar.JarFile.getInputStream(JarFile.java:412)
  - locked <0x00000006905c1bf0> (a sun.net.www.protocol.jar.URLJarFile)
  at sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:162)
  ...

Environment

  • JBoss Enterprise Application Platform
    • 5.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.