Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: EAP 6.0.0
    • Fix Version/s: EAP 6.0.1 ER 3
    • Component/s: None
    • Labels:
      None
    • Environment:

      EAP 6 JDK 1.7

    • Steps to Reproduce:
      Hide

      create a JSF app, deploy it , run it, then undeploy it

      review the heapdumps for hanging objects

      Show
      create a JSF app, deploy it , run it, then undeploy it review the heapdumps for hanging objects
    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      If you dont require JSF in your webapp you can remove faces-context.xml which could have been added by a new project wizard or an archetype, this will prevent JSF from loading and prevent the leak

      Show
      If you dont require JSF in your webapp you can remove faces-context.xml which could have been added by a new project wizard or an archetype, this will prevent JSF from loading and prevent the leak

      Description

      Due to a faulty JSF patch http://java.net/jira/browse/GLASSFISH-15632 which causes InitFacesContext to never get cleared from the ThreadLocal.

      Other objects from same War are also hanging.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ssilvert Stan Silvert
                  Reporter:
                  shay_matasaro Shay Matasaro
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: