[
https://issues.apache.org/jira/browse/WICKET-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702917#action_12702917
]
Andrew Berman commented on WICKET-2232:
---------------------------------------
Juergen, we are on 1.3.5. Unfortunately I don't really have any time to write
up a quickstart. However, we were able to fix the issue. It was due to an
AspectJ injected property on one of our domain objects (which are managed by
Hibernate) not being transient. I'm not sure why we were getting the
StackOverflow, but once we made the property transient, the error ceased.
Nevertheless, I woudln't expect the SerializableChecker to run infinitely even
if something wasn't serializable.
> org.apache.wicket.util.io.SerializableChecker StackOverflow Exception
> ---------------------------------------------------------------------
>
> Key: WICKET-2232
> URL: https://issues.apache.org/jira/browse/WICKET-2232
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Linux/Windows, Tomcat 6, Java 6
> Reporter: Andrew Berman
>
> We are running into this error:
> org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
> Unable to serialize class:
> org.springframework.beans.factory.support.DefaultListableBeanFactory
> But the problem is that once that error occurs it displays the Field
> hierarchy which literally looks like it's running into an infinite loop. It
> goes on for miles in the log files. Eventually it runs into a
> StackOverflowException or OutOfMemory exception.
> There needs to be a way to limit the hierarchy or something. It just keeps
> displaying the same thing over and over and over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
