activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rodrigo Sampaio Vaz (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-2808) connection blocked when using stomp or stomp+ssl
Date Wed, 30 Jun 2010 22:14:51 GMT
connection blocked when using stomp or stomp+ssl
------------------------------------------------

                 Key: AMQ-2808
                 URL: https://issues.apache.org/activemq/browse/AMQ-2808
             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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message