Memory leak on LR61 with JBoss AS7.x

• Type: Bug
• Status: Closed
• Resolution: Won't Fix
• Affects Version/s: 6.1.0 CE GA1
• Fix Version/s: 6.1.1 CE GA2
• Component/s: Performance
• Labels: None
• Environment: LR 6.1.0 GA1 JBoss AS7 bundle

#

1. LR61 on JBoss AS7.0.2 memory leak report
   #

The accompanying files document a memory leak observed with
LR61 on JBoss AS7.0.2. The test compares the AS7 bundle to the
Tomcat bundle. Both environnments were setup very similarily.

In short, the tests produced a saturated OldGen (tenured) space
on AS7 after less than 3 minutes of applying a load with JMeter.

The Tomcat environment did not exhibit such a behavior and behaved well
and predictably for the duration of the load application (10 minutes).

#

1. The test setup is the following:
   #

• LR6.1 GA1 (Tomcat Bundle)
• LR6.1 GA1 (JBoss AS Bundle)
• Same database
• Same portal-ext.properties file
• Both environment configured for Garbage collection logging (-Xloggc:??)
• Only the ROOT.war webapp deployed in both environments
• Same amount of heap and permgen space for both environments

#

1. Test protocol:
   #

• Start VisualVM
• Start JMeter and load attached TestPlan.jmx file
• Launch the LR server
• Start monitor of the server process in VisualVM
• Once the server is up, run the JMeter test
• Observe the GC with Visual GC

#

1. Test results:
   #

lr61-as702-gc.log --> GC log for test run with AS7
lr61-as702-visualvm-snapshot.apps --> VisualVM snapshot for test run with AS7
lr61-tcat7-gc.log --> GC log for test run with Tomcat 7
lr61-tcat7-visualvm-snapshot.apps --> VisualVM snapshot for test run with AS7
readme.txt --> this file
TestPlan.jmx --> JMeter test plan

From the results we can observe the following:

1. AS7 test:

• After about 3 minutes, the old gen space is full and the GC does only Full GCs
  (see line 220+ of lr61-as702-gc.log).
• The full GC is not able to free up any (or very little space)
• The Eden space remains full
• The JVM does not respond as GC takes abut 16% of CPU and is peformed continuously
• We are heading for a OOME

1. Tomcat test:

• The system behaves well for the duration of the load test (10 minutes)
• GC activity consumes less than 1% of CPU
• Full GCs are performed approx. every 60 to 90 sec.
• Heap usage gradually increases and stabilizes after 6 or 7 min

1. Additional notes:

• Similar tests were conducted with JBoss AS71 with similar results.
• Tests were also performed with a heap size of 2048m but the results
  are the same. OldGen staturation just occurs a bit later.