I need to understand what and when Wicket tries to serialize stuff in a running wicket application. I am not able to fix this error and it keeps growing with more users starting to use the application. It does not affect the application usage but it keeps beaming error email.
I am using LRU map to cache certain data being used in the application and that is a shared data in a static context not tied to any particular user. Why would wicket try to serialize this object, this should not be serialized at all. LRU map this is not synchronized and is not thread-safe and application code treats it that way but the serialization keeps generating concurrent modification exception as its obvious its trying to serialize this when something changes the map. if i declare this as transient, will this prevent wicket from serializing this map too, what are the possible repercussion in wicket application if i declare this transient. Thanks for your help. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/How-to-resolve-this-java-util-ConcurrentModificationException-tp4660273p4660725.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
