Anthony, Make sure any objects you store in a session implement the Serializable interface. Tomcat uses serialization to pesrsist sessions and any objects that can not be serialzed will fail to be made persistent durring shutdown. When Tomcat starts back up, session references to these objects will fail.
I don't remember the specific exception thrown, but I would expect it to be a "NullPointerException" instead of a "NoClassDefFoundError". Then again, this might be a common exception that is thrown when de-serializing a incomplete object graph from a binary representation. ~Scott Anthony Martin wrote: >I get the exception, "java.lang.NoClassDefFoundError" from time to time >after starting Tomcat and browsing to certain Servlet mappings. This >exception just goes away if I restart the server, but comes back the next >time I restart the server. > >I have reason to believe that this is cause by persistent session objects. >If so, how do I prevent my session objects from being persistent between >shutdowns? > >Any other ideas besides session persistency? > > >Anthony > >On the other hand, you have different fingers. > >-- >To unsubscribe: <mailto:[EMAIL PROTECTED]> >For additional commands: <mailto:[EMAIL PROTECTED]> >Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > > > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
