0

I am attempting to refactor a large legacy webapp so it will support serialization. During testing I restart the webapp via the Tomcat manager and see serialization exceptions in the console. However, the class which is the culprit (not serializaing correct) isn't shown. I suspect it displayed at the end of the error message (but in the console it just shows, "...28 more" after listing all the standard stack trace.

Is there a simple way to identify which class(es) aren't serializing? Given the size of the app it would be faster and easier if I can find out by looking at log files than manually reviewing every class (many of which aren't session scoped). if the class is indeed listed at the end of the stacktrace, how I can enable Tomcat logging so it writes this to file? (I have a vanilla install of Tomcat within MyEclipse and it doesn't appear to log system messages)

Fred
  • 372
  • 1
  • 6
  • 21
  • after further searching I found the answer (on Stackoverflow no less): http://stackoverflow.com/questions/627389/locating-serialization-issue-in-complex-bea – Fred Feb 09 '12 at 17:56
  • answer for this question is available at http://stackoverflow.com/questions/627389/locating-serialization-issue-in-complex-bean – Fred Feb 23 '12 at 03:55

0 Answers0