11:09 p.m.
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
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
11:11 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) Object isolation verification
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]
Clebert Suconic updated JBMESSAGING-1277:
-----------------------------------------
Attachment: patch.diff
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
11:13 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1277) Object isolation verification
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=comments#action_1... ]
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
10:09 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) Object isolation verification
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]
Clebert Suconic updated JBMESSAGING-1277:
-----------------------------------------
Fix Version/s: 1.4.0.SP3_CP03
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, 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
10:11 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) Object isolation verification
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]
Clebert Suconic updated JBMESSAGING-1277:
-----------------------------------------
Priority: Major (was: Minor)
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
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
3:31 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1277) Object isolation verification
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]
Clebert Suconic closed JBMESSAGING-1277.
----------------------------------------
Resolution: Done
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.0.SP3.CP02, 1.4.1.CR1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Fix For: 1.4.0.SP3_CP03, 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
3:35 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1277) Object isolation verification
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]
Clebert Suconic reopened JBMESSAGING-1277:
------------------------------------------
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.0.SP3.CP02, 1.4.1.CR1
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
3:37 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) ObjectMessage should aways isolate the MessageBody
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]
Clebert Suconic updated JBMESSAGING-1277:
-----------------------------------------
Summary: ObjectMessage should aways isolate the MessageBody (was: Object isolation
verification)
ObjectMessage should aways isolate the MessageBody
--------------------------------------------------
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
3:37 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[ 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
3:44 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1277:
----------------------------------------------
Done on SP, waiting merge on Branch_Stable before I can close this issue
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
1:04 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1277?page=all ]
Clebert Suconic closed JBMESSAGING-1277.
----------------------------------------
Resolution: Done
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: 1.4.0.SP3_CP03, 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
3:04 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.ji...
]
Tim Fox reopened JBMESSAGING-1277:
----------------------------------
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
3:04 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.ji...
]
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
5:54 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.ji...
]
Clebert Suconic closed JBMESSAGING-1277.
----------------------------------------
Resolution: Done
This was applied on both branches, as shown on fishEye.
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
3:15 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.ji...
]
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:15 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.ji...
]
Clebert Suconic reopened JBMESSAGING-1277:
------------------------------------------
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.ji...
]
Clebert Suconic updated JBMESSAGING-1277:
-----------------------------------------
Affects Version/s: (was: 1.4.0.SP3.CP02)
(was: 1.4.0.SP3_CP01)
(was: 1.4.0.SP3)
(was: 1.4.0.SP2)
(was: 1.4.0.SP1)
(was: 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.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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1277) In some edge cases, Object Isolation is broken on ObjectMessage
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1277?page=com.atlassian.ji...
]
Clebert Suconic closed JBMESSAGING-1277.
----------------------------------------
Resolution: Done
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.SP3_CP03
Reporter: Clebert Suconic
Assignee: Clebert Suconic
Fix For: 1.4.1.GA, 1.4.2.GA, 1.4.0.SP3.CP04
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
5713
days inactive
5911
days old
17 comments
2 participants
participants (2)
-
Clebert Suconic (JIRA) -
Tim Fox (JIRA)