Thanks for the reply, Igor. Indeed it was my own error -- there was a misconfiguration in our log4j config which led to me simply not seeing error messages generated by Wicket when serialization failed. It's only when I was shutting down the server, the error message had enough severity to be seen.
On the other hand I found out a tidbit of information that I wanted to share with the community :) Under current Sun JDK, if you set JVM option: -Dsun.io.serialization.extendedDebugInfo=true then any NotSerializableExceptions will include detailed debug information showing where the problem has occurred. This might be useful in cases where SerializationChecker is not immediately available. igor.vaynberg wrote: > > seems like it should be running. > > AbstractPageStore:203 serializes the page by calling > Objects.objectToByteArray() which by default uses > DefaultObjectStreamFactory which in turn runs your object through the > SerializableChecker if an exception occurs, see > IObjectStreamFactory:125 > > so unless you installed your own objectoutputstreamfactory or if you > are running on a non-sun jdk (serializable checker hacks stuff using > reflection) you should be using it... > > -igor > -- View this message in context: http://old.nabble.com/Support-for-serialization-debugging.-tp27820726p27851166.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
