[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1277) Object isolation verification

[Clebert Suconic (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=comments#action_12410385 ] 
            
Clebert Suconic commented on JBMESSAGING-1277:
----------------------------------------------

The only situation in which Object isolation would be broken is if you called objectMsg.getObject(),

or if you called objectMsg.setObject(msg) twice.


On the first case, the returned object would have a shared reference, what means any calls to the object after setObject will also change the object sent.

On the second case, if you called objectMsg.setObject(msg) twice, the second call would be ignored.


This is not a common user's practice. As long as users avoid this behavior,  they should be fine.

> Object isolation verification
> -----------------------------
>
>                 Key: JBMESSAGING-1277
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1277
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.1.CR1, 1.4.0.SP3.CP02
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: Stable branch
>
>         Attachments: patch.diff
>
>
> I believe there is a bug on ObjectMessage as reported by an user.
> On the patch attached there is a testcase validating the Object isolation.
> IMO an ObjectMessage shouldn't cache serialized objects, and it should aways return a new de-serialized object. It is user's responsibility to proper manage calls to getobject in order to not cause performance issues and excessive serialization on this case.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira