activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danilo Tuler (JIRA)" <>
Subject [jira] Commented: (AMQ-2440) stomp+nio leaking file descriptor on client drop
Date Tue, 06 Oct 2009 12:42:53 GMT


Danilo Tuler commented on AMQ-2440:

- Start a server with a single stomp+nio transport. attached.

- Now you need a way to see the TCP ports opened by the server process. netstat will do, but
I'm using "Process Explorer" [1] on Windows XP. Choose the process on the list, go to properties
page, TCP/IP tab.

- For the client I'm using the gozirra library, which is a java stomp client [2]. I think
StompConnection from ActiveMQ would lead to the same issue. But my application already uses
gozirra. Create a client, attached.
No matter if the client calls disconnect or not, the server TCP ports will still be opened
when the client terminates (and won't be reused).


> stomp+nio leaking file descriptor on client drop
> ------------------------------------------------
>                 Key: AMQ-2440
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.3.0
>         Environment: Windows XP
>            Reporter: Danilo Tuler
>            Assignee: Dejan Bosanac
>         Attachments: AMQ-2440-1.txt,,
> The bug is observed on code checkout from
> 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.
> " 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.

View raw message