You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2008/06/05 17:21:00 UTC

[jira] Resolved: (AMQ-1770) BlobUploader gets nulled out when copyMessageOnSend is set to true

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

Rob Davies resolved AMQ-1770.
-----------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

Fixed by SVN revision  663639

> BlobUploader gets nulled out when copyMessageOnSend is set to true
> ------------------------------------------------------------------
>
>                 Key: AMQ-1770
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1770
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.1.0
>            Reporter: Joe Fernandez
>            Assignee: Rob Davies
>            Priority: Minor
>             Fix For: 5.2.0
>
>         Attachments: blobpatch.txt
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> You have to set the "copyMessageOnSend" option to false in order to get the upload to work for an ActiveMQBlobMessage.
> From a user forum thread
> "When the message is created with activeMQSession.createBlobMessage(File), it sets the message's blobUploader field. When the ActiveMQBlobMessage.copy() method is called, it does not copy this field. The new message has a null blobUploader. Then, when the ActiveMQBlobMessage.onSend() gets called, it does not upload the file if the blobUploader field is null."
> I am assuming this to be a bug and not by design. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.