Re: Session Object Serailization

[Shahed Ali]

Hi,   Thanks for the insight, but what I meant was will Tomcat automatically  serialise a session if it grows too large ? Or will it do so only if the server is ready to shutdown.   I do NOT want my session data to be serailzed without my knowing .   Thanks Shahed.   -----Original Message----- From: Craig R. McClanahan <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Tuesday, January 02, 2001 4:45 PM Subject: Re: Session Object Serailization Alef Arendsen wrote: can't you make any object that you cannot make serializable just TRANSIENT so it won't cause any problems??? alef You can do this, *if* you have control over the source of the classes in question, and *if* the class will still operate correctly after the object is reloaded, and the transient instance variable has a null value instead of pointing at something real.  I suspect neither of these is likely to be the case for a JDBC driver that you are using. For example, most JDBC drivers have a buried reference to a java.net.Socket inside their Connection implementations, which is required to perform TCP/IP reads and writes to the database server.  If you mark this variable transient, it will be initialized to null when the object is deserialized and reloaded, so you'll start getting NullPointerException errors -- since the rest of the driver assumes that the socket was initialized at open() time and will not be erased until close().   Craig McClanahan