activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Closed] (AMQ-4650) ActiveMQObjectMessage.setObject behavior when objectMessageSerializationDefered is true
Date Thu, 25 Jul 2013 15:09:50 GMT


Timothy Bish closed AMQ-4650.

    Resolution: Not A Problem

Working as designed.  If you configure delayed serialization of course the changes to the
object will take be reflected up to the time that the object is serialized, its right there
in the name.  If you are using object that are mutated after calling setOject you need to
disable delayed serialization. 
> ActiveMQObjectMessage.setObject behavior when objectMessageSerializationDefered is true
> ---------------------------------------------------------------------------------------
>                 Key: AMQ-4650
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Documentation
>    Affects Versions: 5.8.0
>            Reporter: Chaim Platonov
> The documentation for ActiveMQObjectMessage.setObject says that "an ObjectMessage contains
a snapshot of the object at the time setObject() is called; subsequent modifications of the
object will have no effect on the ObjectMessage body".
> But when objectMessageSerializationDefered on connection is set to true the serialization
happens only when the message is sent, therefore modifications of the object till then WILL

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:

View raw message