activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-1941) Broker hangs on a STOMP client asking for receipts
Date Wed, 29 Jun 2011 14:30:28 GMT

     [ https://issues.apache.org/jira/browse/AMQ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-1941.
-----------------------------

    Resolution: Cannot Reproduce

Not able to reproduce this on a 5.5 broker.

> Broker hangs on a STOMP client asking for receipts
> --------------------------------------------------
>
>                 Key: AMQ-1941
>                 URL: https://issues.apache.org/jira/browse/AMQ-1941
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0, 5.2.0
>            Reporter: Yari Marchetti
>             Fix For: NEEDS_REVIEWED
>
>         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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message