]
Srivathsan Agaram Venkatavaradhan updated WFLY-4617:
----------------------------------------------------
Attachment: merge paths - ArtifactDetailList
Char Array Incoming reference
Char Array Retained Objects
Heap Histogram View
Overall Heap
Overall Memory Usages
Attaching eclipse MAT heap analysis report
Huge garbage created at regular intervals in Wildfly 8.2.0.Final
----------------------------------------------------------------
Key: WFLY-4617
URL:
https://issues.jboss.org/browse/WFLY-4617
Project: WildFly
Issue Type: Bug
Affects Versions: 8.2.0.Final
Environment: Centos 7, JDK 7
Reporter: Srivathsan Agaram Venkatavaradhan
Assignee: Jason Greene
Labels: 8.2.0.Final, gc, undertow, wildfly
Attachments: Char Array Incoming reference, Char Array Retained Objects, Heap
Histogram View, merge paths - ArtifactDetailList, newheap1_Leak_Suspects.zip, Overall
Heap, Overall Memory Usages
Huge garbage is created in wildfly every couple of minutes. Though Full GC is able to
reclaim memory, this causes frequent full gcs as heap is getting occupied due to the
increase in number of objects . I can reproduce this issue in 60 users Jmeter loadtest.
This was not the case in Jaboss 7.1.1Final.
After analyzing heapdumps, I can see huge char arrays are created and they are not
garbage collected by Minor GC. Incoming reference for the char array suggest that they
have valid reference to io.undertow.servlet.spec.HttpServletRequestImpl.
"org.apache.struts.tiles.ComponentContext" is kept in attributes Map by
io.undertow.servlet.spec.HttpServletRequestImpl. org.apache.struts.tiles.ComponentContext
contains a big char array.
We suspect issue with undertow.