You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Patrick Twohig (JIRA)" <ji...@apache.org> on 2012/11/02 07:38:12 UTC

[jira] [Updated] (VYSPER-332) Memory Leak in BoshBackedSessionContext

     [ https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Twohig updated VYSPER-332:
----------------------------------

    Description: I'm seeing the heap size grow disproportionately large when running the BoshServlet in my web application.  Specifically, I am seeing the  consume 300+ megabytes of heap causing an OOME.  The heap dump indicates that roughly 85% of my memory is consumed but the single instanced of .  I can provide a heap dump if needs be.  (was: I'm seeing the heap size grow disproportionately large when running the BoshServlet in my web application.  Specifically, I am seeing the BoshBackedServletSessionContext consume 300+ megabytes of heap causing an OOME.  The heap dump indicates that roughly 85% of my memory is consumed but the single instanced of BoshBackedServletSessionContext.  I can provide a heap dump if needs be.)
    
> Memory Leak in BoshBackedSessionContext
> ---------------------------------------
>
>                 Key: VYSPER-332
>                 URL: https://issues.apache.org/jira/browse/VYSPER-332
>             Project: VYSPER
>          Issue Type: Bug
>          Components: BOSH
>    Affects Versions: 0.7
>         Environment:  - Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-31-virtual x86_64)
>  - OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
>  - Jetty 6.1.24
>            Reporter: Patrick Twohig
>
> I'm seeing the heap size grow disproportionately large when running the BoshServlet in my web application.  Specifically, I am seeing the  consume 300+ megabytes of heap causing an OOME.  The heap dump indicates that roughly 85% of my memory is consumed but the single instanced of .  I can provide a heap dump if needs be.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira