activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3497) STOMP subscription receipt can be out of order with message dispatch, resulting in consumer/client error
Date Wed, 14 Sep 2011 10:49:09 GMT

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

Gary Tully resolved AMQ-3497.
-----------------------------

    Resolution: Fixed

fix in http://svn.apache.org/viewvc?rev=1170523&view=rev

a subscription receipt is now delivered eagerly, it does not wait for the broker subscription
response, such that it cannot be preceded by a message delivery.

> STOMP subscription receipt can be out of order with message dispatch, resulting in consumer/client
error
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3497
>                 URL: https://issues.apache.org/jira/browse/AMQ-3497
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.4.2, 5.5.0
>         Environment: stomp
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: activemq, receipt, stomp
>             Fix For: 5.6.0
>
>
> When a receipt[1] is specified on a subscribe frame, it is possible that a message dispatch
on the newly created subscription gets delivered  before the RECEIPT, causing a stomp client
to error out. The perl client  http://search.cpan.org/~lcons/Net-STOMP-Client-1.1/ gives
> {code}*** unexpected RECEIPT frame received: xxx {code}
> [1] http://stomp.github.com/stomp-specification-1.1.html#Header_receipt

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message