[
https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489655#comment-13489655
]
Bernd Fondermann commented on VYSPER-332:
-----------------------------------------
If the client is gone, his session will time out eventually and the
SessionContext should be collected, freeing all memory. Maybe you are running
in some bug we don't know yet.
What kind of OOME are you seeing? Is your old generation really filled up or
are you experiencing OOME in young/tenure generation?
300 MB of heap is not that much nowadays. Are you in a resource-limited
environmen? How many messages are in the qeue? (I presume its sentResponses?)
What is the average message size?
I agree that there should be the option to configure an upper limit, but an
assumption like (100 msg should be enough) only arbitrarily limits throughput.
> 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
