OK, this fixed it.  I searched through my code for StreamTokenizers and 
found one that was a field of one of my classes, though it hadn't seemed to 
me like that class should ever have been involved in the serialization 
of "searchResults".  Nonetheless, making that transient (as well as one 
other object in that class) did the trick.  Thanks!

-john

> 
> Do any of the objects that you know to be serializing (ala session
> variable 'searchResults' refer to a StreamTokenizer? It might be
> possible that you need to stick a transient keyword infront of an
> objects StringTokenizer field. 
> 
> If you are not sure, you could try serializing your 'searchResults'
> object outside of Tomcat to see if you get the same problem.
> 
> - Chris
> 
> Brainbench MVP Java2
> 
> 
>> -----Original Message-----
>> From: John J Brecht [mailto:[EMAIL PROTECTED]]
>> Sent: 04 October 2001 23:40
>> To: Tomcat
>> Subject: Serialization
>> 
>> 
>> Despite the fact that serialver shows all the objects that my app uses
>> to be serializable, i still get a NotSerializableException when I shut
>> down tomcat.
>> 
>> 2001-10-04 15:32:15 StandardManager[/DLServlet] Cannot 
>> serialize session
>> attribute searchResults for session 84F5340285B3698849421230B8D9B2C3
>> java.io.NotSerializableException: java.io.StreamTokenizer
>>      at java.io.ObjectOutputStream.outputObject(Unknown Source)
>> 
>> 
>> The mysterious thing about this exception, is that the unserializable
>> class in question is not even being used.  The 
>> "searchResults" object is
>> an array of objects of mine that implement Serializable and pass the
>> serialver test.
>> 
>> At any rate, what is the impact of this exception?  sometimes when i
>> restart Tomcat, i find it in an unstable state (won't load pages and
>> doesn't display error messages) and i am wondering of this is the
>> problem.  if so, is there any way that i can circumvent it?  i've
>> already done everything i could to ensure that all of my objects that
>> might be written to the session are serializable.
>> 
>> 
>> thanks!
>> 
>> -john
>> 
> 
> 
> --
> 
> NOTICE:  The information contained in this electronic mail transmission
> is intended by Convergys Corporation for the use of the named
> individual or entity to which it is directed and may contain
> information that is privileged or otherwise confidential.  If you have
> received this electronic mail transmission in error, please delete it
> from your system without copying or forwarding it, and notify the
> sender of the error by reply email or by telephone (collect), so that
> the sender's address records can be corrected.


Reply via email to