OK, your Message object is not PojoCacheable, but in its object graph is a ref to a Collection/Map proxy that PojoCache has created (i.e. it's a Collection/Map that's stored in the cache either directly or as a field of a PojoCacheable object.)
This leads to http://jira.jboss.com/jira/browse/JBCACHE-830. Workarounds: 1) Make Message PojoCacheable. If all the classes are PojoCacheable, the cache can detect this kind of situation and deal with it. 2) Figure out where the ref to the cached Collection/Map is coming from. Change the code so a defensive copy of it is stored instead of a reference to the same object. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982686#3982686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982686 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
