thanks a a lot. I found the object that did not implement Serializable.
On Mon, Jul 28, 2014 at 1:56 PM, Martin Grigorov-4 [via Apache Wicket] < ml-node+s1842946n4666765...@n4.nabble.com> wrote: > Hi, > > Wicket will use CheckingObjectOutputStream in DEV mode only if the normal > serialization has failed with NotSerializableException before that, to > give > you a better explanation which field in which class is the problem: > > https://github.com/apache/wicket/blob/442932d4e4c5cc27940bc2ef956cb24c1ba54df0/wicket-core/src/main/java/org/apache/wicket/serialize/java/JavaSerializer.java#L262 > > Put a breakpoint inside the catch and see which class causes the > NotSerializableException before the usage of CheckingObjectOutputStream. > > I have no idea why it fails with StackOverflowError. > > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > > On Sun, Jul 27, 2014 at 9:01 PM, hoosssein <[hidden email] > <http://user/SendEmail.jtp?type=node&node=4666765&i=0>> wrote: > > > I'm using Wicket 6.15 and I got following exception in my program > > > > java.lang.StackOverflowError > > at java.lang.Exception.<init>(Exception.java:102) > > at > > > > > java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89) > > > at > > > > > java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72) > > > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > > at > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > > at java.lang.reflect.Method.invoke(Method.java:606) > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.internalCheck(CheckingObjectOutputStream.java:398) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.check(CheckingObjectOutputStream.java:361) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.checkFields(CheckingObjectOutputStream.java:645) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.internalCheck(CheckingObjectOutputStream.java:569) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.check(CheckingObjectOutputStream.java:361) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.checkFields(CheckingObjectOutputStream.java:645) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.internalCheck(CheckingObjectOutputStream.java:569) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.check(CheckingObjectOutputStream.java:361) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.checkFields(CheckingObjectOutputStream.java:645) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.internalCheck(CheckingObjectOutputStream.java:569) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.check(CheckingObjectOutputStream.java:361) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.checkFields(CheckingObjectOutputStream.java:645) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.internalCheck(CheckingObjectOutputStream.java:569) > > > at > > > > > org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.check(CheckingObjectOutputStream.java:361) > > > ... > > > > I have no idea what can cause such StackOverFlow in wicket-core. > > > > I search for this exception and found that these part of exception are > > belongs to Serialization. so I checked all of my object and all of them > > implements Serializable > > > > an other interesting port of problem is that this exception doesn't > occurs > > at the first time, It occurs after i try to render component 2 or 3 > time. > > > > Any help would be greatly appreciated. > > > > -- > > View this message in context: > > > http://apache-wicket.1842946.n4.nabble.com/Wicket-StackOverflowError-in-Serializing-or-Seserializing-Session-tp4666758.html > > Sent from the Users forum mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [hidden email] > <http://user/SendEmail.jtp?type=node&node=4666765&i=1> > > For additional commands, e-mail: [hidden email] > <http://user/SendEmail.jtp?type=node&node=4666765&i=2> > > > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://apache-wicket.1842946.n4.nabble.com/Wicket-StackOverflowError-in-Serializing-or-Seserializing-Session-tp4666758p4666765.html > To unsubscribe from Wicket StackOverflowError in Serializing or > Seserializing Session, click here > <http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4666758&code=aG9vc3NzZWluQGdtYWlsLmNvbXw0NjY2NzU4fC04MzkxNzQ2MA==> > . > NAML > <http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- Hossein Nasr Esfahani B.Sc. Student of Computer Engineering khorshid.ut.ac.ir/~h.nasr -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-StackOverflowError-in-Serializing-or-Seserializing-Session-tp4666758p4666837.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org