You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2010/11/10 01:57:00 UTC

[jira] Created: (AMQNET-292) Properties are set to ReadOnly after sending message with CopyOnSend semantics.

Properties are set to ReadOnly after sending message with CopyOnSend semantics.
-------------------------------------------------------------------------------

                 Key: AMQNET-292
                 URL: https://issues.apache.org/activemq/browse/AMQNET-292
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: ActiveMQ
    Affects Versions: 1.4.0, 1.4.1
         Environment: .NET 2.0, .NET 4.0
            Reporter: Jim Gomes
            Assignee: Jim Gomes
             Fix For: 1.5.0


When a message is sent, the producer will make a copy of the message if the copy on send option is on, so that the client can re-use the original message.  However, the internal PropertyHelper does not get duplicated in the cloning operation, and the properties of the message remain in read-only mode and will throw an exception if they are modified.

The PropertyHelper member needs to be cloned during the copy-on-send semantics.

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

[jira] Closed: (AMQNET-292) Properties are set to ReadOnly after sending message with CopyOnSend semantics.

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQNET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes closed AMQNET-292.
----------------------------


> Properties are set to ReadOnly after sending message with CopyOnSend semantics.
> -------------------------------------------------------------------------------
>
>                 Key: AMQNET-292
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-292
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>    Affects Versions: 1.4.0, 1.4.1
>         Environment: .NET 2.0, .NET 4.0
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>             Fix For: 1.5.0
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> When a message is sent, the producer will make a copy of the message if the copy on send option is on, so that the client can re-use the original message.  However, the internal PropertyHelper does not get duplicated in the cloning operation, and the properties of the message remain in read-only mode and will throw an exception if they are modified.
> The PropertyHelper member needs to be cloned during the copy-on-send semantics.

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

[jira] Resolved: (AMQNET-292) Properties are set to ReadOnly after sending message with CopyOnSend semantics.

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQNET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes resolved AMQNET-292.
------------------------------

    Resolution: Fixed

Added new Clone() override function in ActiveMQMessage to copy the MessagePropertyIntercepter object.

> Properties are set to ReadOnly after sending message with CopyOnSend semantics.
> -------------------------------------------------------------------------------
>
>                 Key: AMQNET-292
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-292
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>    Affects Versions: 1.4.0, 1.4.1
>         Environment: .NET 2.0, .NET 4.0
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>             Fix For: 1.5.0
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> When a message is sent, the producer will make a copy of the message if the copy on send option is on, so that the client can re-use the original message.  However, the internal PropertyHelper does not get duplicated in the cloning operation, and the properties of the message remain in read-only mode and will throw an exception if they are modified.
> The PropertyHelper member needs to be cloned during the copy-on-send semantics.

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