[jboss-jira] [JBoss JIRA] (WFLY-4617) Huge garbage created at regular intervals in Wildfly 8.2.0.Final

[Stuart Douglas (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13075514#comment-13075514 ] 

Stuart Douglas commented on WFLY-4617:
--------------------------------------

I have done some local testing and I am not sure if the include() call itself is at fault, it does have a small amount of overhead, but nothing that could account for the difference you are seeing (in my local testing accessing a page via include was less than 1% slower than accessing it directly, and this was essentially a no-op page, so even that was probably exaggerated compared to a real world figure).

Most likely it is something triggered by the include, instead of the include itself. Is there any chance you could get hold of some profile data? 

> 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: Stuart Douglas
>              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 created . We can reproduce this issue in 60 users Jmeter loadtest. This was not the case in Jboss 7.1.1Final. 
> After analyzing heapdumps,   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. However full gc is able to recover the memory. Not sure why attributes in  io.undertow.servlet.spec.HttpServletRequestImpl are not getting gced by minor gc's.
> "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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)