[
https://issues.apache.org/jira/browse/AMQ-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999346#comment-12999346
]
Andreas JAbs edited comment on AMQ-2808 at 2/25/11 1:29 PM:
------------------------------------------------------------
I can confirm this issue also with 5.4.2. on windows xp and server 2008
HOWTO REPRODUCE:
* 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
EDIT: It might also be related to AMQ-1376
The stack trace of the failed reconnect is appended, although it is not the
cause of the bug.
---
received an error javax.jms.InvalidClientIDException: Broker: DzDefaultbroker -
Client: myclient already connected from /xx.xx.xx.xx:2743
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:216)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:77)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:89)
at
org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:676)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:83)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:134)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:300)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at
org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:82)
...
was (Author: ajabs):
I can confirm this issue also with 5.4.2. on windows xp and server 2008
HOWTO REPRODUCE:
* 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: https://issues.apache.org/jira/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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
