]
Clebert Suconic updated JBMESSAGING-1277:
-----------------------------------------
Fix Version/s: 1.4.1.GA
Affects Version/s: 1.4.0.SP3_CP03
1.4.0.SP3.CP02
1.4.0.SP3_CP01
1.4.0.SP3
1.4.0.SP2
1.4.0.SP1
1.4.0.GA
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
Affects Versions: 1.4.0.GA, 1.4.0.SP1, 1.4.0.SP2, 1.4.0.SP3, 1.4.0.SP3_CP01,
1.4.0.SP3.CP02, 1.4.0.SP3_CP03
Reporter: Clebert Suconic
Assignee: Clebert Suconic
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA, 1.4.2.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: