activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (APLO-333) ACK does not remove the message when calling from different conenction
Date Fri, 02 Aug 2013 10:11:50 GMT

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

Timothy Bish moved AMQ-4664 to APLO-333:
----------------------------------------

    Component/s:     (was: Apollo)
                 apollo-stomp
            Key: APLO-333  (was: AMQ-4664)
        Project: ActiveMQ Apollo  (was: ActiveMQ)
    
> 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

Mime
View raw message