activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas JAbs (JIRA)" <>
Subject [jira] Commented: (AMQ-2808) connection blocked when using stomp or stomp+ssl
Date Fri, 25 Feb 2011 13:03:40 GMT


Andreas JAbs commented on AMQ-2808:

I can confirm this issue also with 5.4.2. on windows xp and server 2008

* start broker with stomp connector enabled
* use any stomp client to connect and subscribe to a topic
* kill client without a disconnect
* reconnect client
-> subscribe will fail

If one kills the TransportConnector associated with the client via JMX, the connect is possible.

I think the bug might be somehow related to AMQ-2511

> connection blocked when using stomp or stomp+ssl
> ------------------------------------------------
>                 Key: AMQ-2808
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Transport
>    Affects Versions: 5.3.2
>         Environment: Linux 64 bit, debian, sun java 1.6.0_20
>            Reporter: Rodrigo Sampaio Vaz
> When a client opens a connection and unexpectedly finishes the connection remains open
and established on the activemq machine, follow are the steps to reproduce:
> 1 - Start the activemq using the stomp connector or stomp+ssl 
> 2 - Use tcpkill -9 port 61612 (default por for stomp connector)
> 3 - From another machine send a telnet connection to the stomp port like telnet <stomp_server_ip>
<stomp_port>, this connection is going to be finished by tcpkill
> 4 - On the activemq machine issue a netstat -pont | grep <stomp_port>
> You should  see that a connection is still ESTABLISHED and the number of connections
grows if you start more telnets to the port. To the activemq server it thinks that the clients
are still connected even if they are dead.
> This does not happens when using stomp+nio, but since there is no ssl over stomp+nio
we loose the encryption.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message