activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4002) Instance of BlobTransferPolicy and its URL are being shared among multiple messages
Date Sat, 08 Sep 2012 11:05:07 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451309#comment-13451309
] 

Claus Ibsen commented on AMQ-4002:
----------------------------------

I am fixing this in the BlobUploader and BlobDownloader so they do a copy of the policy.
                
> Instance of BlobTransferPolicy and its URL are being shared among multiple messages
> -----------------------------------------------------------------------------------
>
>                 Key: AMQ-4002
>                 URL: https://issues.apache.org/jira/browse/AMQ-4002
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.6.0
>         Environment: Tested on Debian Lenny 64
> ActiveMQ 5.6.0
>            Reporter: Antoine Libert
>            Assignee: Claus Ibsen
>            Priority: Critical
>              Labels: BlobTransferPolicy, ftp, url
>             Fix For: 5.7.0
>
>         Attachments: amq_patch.diff
>
>
> Bug we encountered: using BlobMessage (FTP backend) and individual acknowledge, URL of
BlobTransferPolicy was shared among messages following the acknowledge of messages.
> Example: 1 queue, 1 consumer, 1 producer, prefetch limit 5 messages
> - Producer generated 10 messages
> - Consumer received and processed (but do not ack) 5 messages
> - Consumer acked the 5 messages in a row
> - Consumer received 5 more messages and the first one shared the same BlobTransferPolicy
and FTP URL that the last acknowledged messages.
> We tested the attached (one line) patch in our production server for more than one month
and it did not the show the bug or any new one.

--
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