Hi, Wicket 6.x has org.apache.wicket.core.util.objects.checker.IObjectChecker. You may create your own one that doesn't allow serialization of LRUMap. When such object is passed to ObjectOutputStream it will throw an exception with nice message explaining the reference to this LRUMap. This way you should be able to find which page keeps a ref to the LRUMap See org.apache.wicket.serialize.java.JavaSerializer.SerializationCheckerObjectOutputStream#writeObjectOverride for an example how to add your checker
On Tue, Aug 6, 2013 at 8:03 PM, saty <[email protected]> wrote: > Ok.. To explain the scenario, i have a singleton data-maanger java class > that > user a underlying LRUMAP to store most recently viewed data. various wicket > panels use this data-manager to request data that they need to > display/update etc. > Access to data is well protected using various synchronization techniques > and have no problem in that. The problem seems to be, is somehow wicket is > trying to serialize this LRUMAP which conflicts with application wring data > to it at that same time. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/How-to-resolve-this-java-util-ConcurrentModificationException-tp4660273p4660730.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] > >
