[
https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489520#comment-13489520
]
Patrick Twohig commented on VYSPER-332:
---------------------------------------
I'll give Trunk a try for sure. My big question is, why isn't that queue
bounded? I would assume once you get to a certain number of messages waiting
to be sent, it should just assume the user has gone away and isn't eligible for
incoming messages. I have a sneaking suspicion what's happening in my
situation is we have a buggy client that's flooding the server. Correct me if
I'm wrong, but a single user shouldn't expect to get more than maybe ~100
messages queued up. Why not also drop the session when the user hits some
limit?
> 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
