4:14 p.m.
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PojoCache
Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA,
1.2.4SP2
Reporter: Brian Stansberry
Assigned To: Ben Wang
The PojoCache Collection and Map proxies implement Serializable via List but don't do
anything to override default serialization. They have non-transient fields with refs to
things like the cache itself, so serializing one of these is a big problem -- you
serialize the whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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
4:23 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-830) Incorrect serialization of Collection and Map proxies
[ http://jira.jboss.com/jira/browse/JBCACHE-830?page=all ]
Brian Stansberry updated JBCACHE-830:
-------------------------------------
Description:
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
was:
The PojoCache Collection and Map proxies implement Serializable via List but don't do
anything to override default serialization. They have non-transient fields with refs to
things like the cache itself, so serializing one of these is a big problem -- you
serialize the whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA,
1.2.4SP2
Reporter: Brian Stansberry
Assigned To: Ben Wang
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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:03 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-830) Incorrect serialization of Collection and Map proxies
[ http://jira.jboss.com/jira/browse/JBCACHE-830?page=comments#action_12346181 ]
Brian Stansberry commented on JBCACHE-830:
------------------------------------------
In previous comment about not being sure about solution, I was thinking in terms of a
non-PojoCacheable but serializable object that has a ref to a Collection/Map proxy. If
you place that in the cache, how do you ensure that on the recipient node, the object
relationship to the cached Colleciton/Map is maintained? But actually I don't think
that's a requirement at all -- once you place a non-PojoCacheable object in the cache,
any expectation of maintaining object relationships on other nodes is gone.
So, I think the correct solution is to use writeReplace().
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.3.0.GA, 1.4.0.GA, 1.2.4SP2, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3,
1.4.0.SP1
Reporter: Brian Stansberry
Assigned To: Ben Wang
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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
4:13 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-830) Incorrect serialization of Collection and Map proxies
[ http://jira.jboss.com/jira/browse/JBCACHE-830?page=comments#action_12346194 ]
Ben Wang commented on JBCACHE-830:
----------------------------------
See this design forum thread for further discussion.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982840#...
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.3.0.GA, 1.4.0.GA, 1.2.4SP2, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3,
1.4.0.SP1
Reporter: Brian Stansberry
Assigned To: Ben Wang
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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:28 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-830) Incorrect serialization of Collection and Map proxies
[ http://jira.jboss.com/jira/browse/JBCACHE-830?page=all ]
Ben Wang updated JBCACHE-830:
-----------------------------
Fix Version/s: 2.0.0.GA
Also need this in 1.4 src
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.3.0.GA, 1.4.0.GA, 1.2.4SP2, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3,
1.4.0.SP1
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: 2.0.0.GA
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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
5:07 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-830) Incorrect serialization of Collection and Map proxies
[ http://jira.jboss.com/jira/browse/JBCACHE-830?page=comments#action_12346675 ]
Ben Wang commented on JBCACHE-830:
----------------------------------
I have taken a look closely. Turns out that the Collection ClassProxy can actually
serializie correctly. Classes like CachedMapImpl doesn't need to be Seriaizable
because CachedMapInterceptor, e.g., will do a reflection on the CachedMapImpl. The
original forum post's problem lies elsewhere. It complains of MarshalledClassProxy
where we use only ClassProxy in Collection. So it maybe a leak from AS side. Anyway, I
think it is a corner case now.
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA,
1.2.4SP2
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: 2.0.0.GA
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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
5:09 a.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-830) Incorrect serialization of Collection and Map proxies
[ http://jira.jboss.com/jira/browse/JBCACHE-830?page=all ]
Ben Wang resolved JBCACHE-830.
------------------------------
Resolution: Rejected
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA,
1.2.4SP2
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: 2.0.0.GA
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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
8:29 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-830) Incorrect serialization of Collection and Map proxies
[ http://jira.jboss.com/jira/browse/JBCACHE-830?page=all ]
Manik Surtani updated JBCACHE-830:
----------------------------------
Fix Version/s: (was: 2.0.0.GA)
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL: http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.3.0.GA, 1.4.0.GA, 1.2.4SP2, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3,
1.4.0.SP1
Reporter: Brian Stansberry
Assigned To: Ben Wang
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
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
6179
days inactive
6451
days old
7 comments
3 participants
participants (3)
-
Ben Wang (JIRA) -
Brian Stansberry (JIRA)
-
Manik Surtani (JIRA)