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

Clebert Suconic (JIRA) jira-events at lists.jboss.org
Mon Jun 30 09:37:33 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]

Clebert Suconic updated JBMESSAGING-1277:
-----------------------------------------

    Summary: In some edge cases, Object Isolation is broken on ObjectMessage  (was: ObjectMessage should aways isolate the MessageBody)

> In some edge cases, Object Isolation is broken on ObjectMessage
> ---------------------------------------------------------------
>
>                 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
>             Fix For: Stable branch, 1.4.0.SP3_CP03
>
>         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

        



More information about the jboss-jira mailing list