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

Seam and JBoss-el upgrade due "High CPU usage because of concurrent use of WeakHashmap"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.0, EAP_EWP 5.1.1
    • Seam
    • None
    • Hide
      The org.apache.el.util.concurrentcache class did not synchronize requests for concurrent access to WeakHashMap. In some cases, this caused an infinite loop, which consumed excessive CPU memory. The underlying issue has now been resolved and access to WeakHashMap in the org.jboss.el.util.concurrentcache class is now synchronized.
      Show
      The org.apache.el.util.concurrentcache class did not synchronize requests for concurrent access to WeakHashMap. In some cases, this caused an infinite loop, which consumed excessive CPU memory. The underlying issue has now been resolved and access to WeakHashMap in the org.jboss.el.util.concurrentcache class is now synchronized.
    • Documented as Resolved Issue
    • NEW

      Concurrent access to WeakHashmap by org.jboss.el.util.ConcurrentCache causes High CPU.
      This issue is similar to https://issues.jboss.org/browse/JBWEB-185 because they use the same codebase.

            mnovotny@redhat.com Marek Novotny
            mark_v_torres Mark Torres (Inactive)
            Eva Kopalova Eva Kopalova (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: