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"

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.0, EAP_EWP 5.1.1
    • Fix Version/s: EAP_EWP 5.1.2 ER1
    • Component/s: Seam
    • Labels:
      None
    • Release Notes Text:
      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.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  mark_v_torres Mark Torres
                  Writer:
                  Eva Kopalova
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: