[ 
https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496008#comment-13496008
 ] 

Patrick Twohig commented on VYSPER-332:
---------------------------------------

I found a comment in the AbstractSessionContext class indicating that the 
resource the resource registry doesn't handle the situation where a client 
"goes berserk" and could cause a DoS attack.  Would that be related?

I also noticed in the BoshHandler that the BoshBackedSessionContext writes a 
stanza before finally closing it.  I was curious if maybe that write before 
closing was inadvertently keeping the session along for much longer than 
intended.  I traced through the code as best I could, but wasn't able to make 
sense of it.  My suspicion was that a session is lingering around unable to 
deliver messages to a client they just keep stacking up.  Thought the 
inactivity checker will purge them it seems like it may take longer than 
expected.  Is that a possibility?

At what point does the BoshBackedSessionContext actually get placed in the 
registry?
                
> 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
>         Attachments: log_tail.txt
>
>
> 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

Reply via email to