You're trying to serialize something that doesn't want to be serialized. I guess ths solution is to take that object out of the stuff being serialized.
Can you tell from the stack trace what it is going on when this happens? We had this once because we use session persistence, we put something bad on the session and WebSphere serializes the session to save it to database.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com