[
https://issues.apache.org/activemq/browse/AMQ-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-2440.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.4.0
This is now fixed on trunk and 5.3 branch. It's tested manually using
StompLoadTest in activemq-systest subproject, which opens/closes a connection
for every send/receive and simulates a real load on the broker. This test
should be converted to the real system test, but that's the case for another
issue.
> stomp+nio leaking file descriptor on client drop
> ------------------------------------------------
>
> Key: AMQ-2440
> URL: https://issues.apache.org/activemq/browse/AMQ-2440
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.3.0
> Environment: Windows XP
> Reporter: Danilo Tuler
> Assignee: Dejan Bosanac
> Fix For: 5.3.1, 5.4.0
>
> Attachments: AMQ-2440-1.txt, StompDropTestConsumer.java,
> StompDropTestServer.java
>
>
> The bug is observed on code checkout from
> https://svn.apache.org/repos/asf/activemq/tags/activemq-5.3.0
> A server is initiated with stomp+nio transport on port 61612.
> A client connects. A SelectorWorker is created on SelectorManager:68.
> If the client drops the connection an exception is received at
> StompNIOTransport:91.
> "java.io.IOException: An existing connection was forcibly closed by the
> remote host".
> But selector are not cleaned up. It works with stomp transport. But not with
> stomp+nio.
> What I see in the end is an increasing number of "connections" if the JVM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
