Details

    • Steps to Reproduce:
      Hide
      • Build the project
      • Deploy generated WAR file to WildFly
      • Execute the bash script
        for i in {1..10}; do curl http://localhost:8080/wildfly-oome/; done
        
      • Requests start failing with java.lang.OutOfMemoryError: Java heap space
      Show
      Build the project Deploy generated WAR file to WildFly Execute the bash script for i in {1..10}; do curl http: //localhost:8080/wildfly-oome/; done Requests start failing with java.lang.OutOfMemoryError: Java heap space

      Description

      https://github.com/konbk/bug-report-wildfly-oome

      The project shows a huge memory leak introduced in recent WildFly versions that can crash a real-world Java EE application in a matter of hours.

      When a JSF page contains any component bound to page variable, all CDI beans (regardless of scope) used on that page stay in memory.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  flavia.rainone Flavia Rainone
                  Reporter:
                  konbk Konrad Bak
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: