Subject | Re: java.io.NotSerializableException |
---|---|
Author | Roman Rokytskyy |
Post date | 2003-06-20T11:20:34Z |
Hi,
serialization it will close the connection, and after de-serializing
it will restore connection to the database from the point when it
disconnected?
In general, it is a very bad idea to store connection in the session.
In particular, you cannot serialize session, since java.sql.Connection
is not serializable.
Best regards,
Roman Rokytskyy
> It happens very hardly ever after compiling changes and reloadingI think keyword here is "reload it again".
> some JSP beans into Tomcat.
>
> The solution is recompile the same code, without adding any new
> change, and reload it again.
> 2003-05-23 13:17:14 StandardManager[/wasp] IOException while loadingWhy do you store connections in http sessions? Do you expect that on
> persisted sessions: java.io.WriteAbortedException: writing aborted;
> java.io.NotSerializableException: org.firebirdsql.jdbc.FBConnection
> java.io.WriteAbortedException: writing aborted;
> java.io.NotSerializableException: org.firebirdsql.jdbc.FBConnection
serialization it will close the connection, and after de-serializing
it will restore connection to the database from the point when it
disconnected?
In general, it is a very bad idea to store connection in the session.
In particular, you cannot serialize session, since java.sql.Connection
is not serializable.
Best regards,
Roman Rokytskyy