[
https://issues.apache.org/jira/browse/AMQ-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-2844.
-----------------------------
Resolution: Cannot Reproduce
Cannot reproduce, reopen if a test case can be generated that demonstrates the
problem.
> Handle leak when out-of-memory
> ------------------------------
>
> Key: AMQ-2844
> URL: https://issues.apache.org/jira/browse/AMQ-2844
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.2
> Environment: Windows Server 2003 Ent, tomcat 60.028, jre 6
> Reporter: Chuck Liu
> Priority: Critical
>
> To reproduce this bug:
> At the server side, set memory pool of JVM to 20MB.
> At client side, start 30 threads, keep sending messages to ActiveMQ.
> Soon, the ActiveMQ will report out-of-memory.
> But in the exception handler, it didn't close the socket.
> Type netstat -an, you will see a lot of connections in state CLOSE_WAIT.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
