[
https://issues.apache.org/activemq/browse/AMQ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45802#action_45802
]
Yari Marchetti commented on AMQ-1941:
-------------------------------------
i made some more research on this issue and have some more informations.
This bug seems to happen when there's a subscription active with ack mode set
to 'auto' and then, asking the broker for a receipt for every following command
issued. This lead the broker to hang not sending any receipts nor other
messages, and not be able to close the socket as well.
> Broker hangs on a STOMP client asking for receipts
> --------------------------------------------------
>
> Key: AMQ-1941
> URL: https://issues.apache.org/activemq/browse/AMQ-1941
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0, 5.2.0
> Reporter: Yari Marchetti
> Attachments: test.pl
>
>
> Using STOMP protocol, under some circumstances, asking for a command receipt
> (by adding a "receipt:<unique-identifier>" header) leads the broker in a
> status where it won't answer nor it will let close the socket.
> By running the attached perl scripts some times, first it will complete
> cleanly, by sending and receiving all messages correctly, but later it won't,
> because it will hang on waiting for a command receipt from the broker that
> never comes.
> Once in this status, the broker won't stop gracefully using the
> 'activemq-admin stop' because it won't be able to close the socket that once
> had the client attached. In the activemq.log (or by looking at standard
> output) a:
> The connection to '/x.x.x.x:x' is taking a long time to shutdown
> will be generated every 5 seconds.
> Tested with both 5.1 and latest snapshot of 5.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
