You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Namrata (JIRA)" <ji...@apache.org> on 2013/08/27 14:33:53 UTC

[jira] [Resolved] (APLO-333) ACK does not remove the message when calling from different conenction

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

Namrata resolved APLO-333.
--------------------------

    Resolution: Fixed

Yes. I guess i was expecting something like stomp 1.1 where message-id is unique, so when u ACK using message-id from any connection it shouldn't matter. But stomp 1.2 is different.

Thanks.
                
> ACK does not remove the message when calling from different conenction
> ----------------------------------------------------------------------
>
>                 Key: APLO-333
>                 URL: https://issues.apache.org/jira/browse/APLO-333
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-stomp
>         Environment: Apollo 1.6
>            Reporter: Namrata
>         Attachments: ack_problem_stomp1.2.log
>
>
> I am using Apollo 1.6 and stomp 1.2.
> I was trying to update the FuseSource php stomp lib for 1.2, and am stuck with this scenario.
> 1) Connect to Apollo
> 2) Subscribe to "testQ" using ack=client-individual
> 3) Read message $msg
> 4) Disconnect
> //-- Some processing with this message, if processing was success
> 5) Open a  new connection to Apollo
> 6) Subscribe to "testQ" using ack=client-individual
> 7) ACK the $msg from above using just the "id", "message-id", "ack" headers.
> The result frame is correct, but the message won't get deleted from Apollo. Is there something wrong with the way i am doing it?
> (Attached stomp commands log)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira