[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox updated JBMESSAGING-1277:
---------------------------------

        Fix Version/s:  1.4.0.SP3.CP04
                       1.4.1.GA
                           (was: Stable branch)
                           (was: 1.4.0.SP3_CP03)
    Affects Version/s:     (was: 1.4.0.SP3.CP02)
                           (was: 1.4.1.CR1)


> In some edge cases, Object Isolation is broken on ObjectMessage
> ---------------------------------------------------------------
>
>                 Key: JBMESSAGING-1277
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1277
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>             Fix For:  1.4.0.SP3.CP04, 1.4.1.GA
>
>         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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira