db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Fischer <fisc...@seitenbau.net>
Subject RE: NPE when reading LargeSelect objects from serialized storage
Date Mon, 30 Jan 2006 13:06:42 GMT
Just an observation which might be relevant for this:
>From my experience with Tomcat and Torque, it seems to me (though I never
checked it) that Tomcat first deserializes the session, and then
initializes the application where the session belongs to. If this is true,
this is problematic if the deserialzed objects cannot exist without Torque
being initialized.

         Thomas

Thomas Vandahl <thomas.vandahl@tewisoft.de> schrieb am 30.01.2006 09:47:55:

> I just want to know if anybody can reproduce this:
>
> I use Torque and Turbine in a web application. The application is
> deployed to Tomcat 5.0. Now if Tomcat reloads the application (which
> happens quite often during development and debugging), the sessions will
> be serialized and de-serialized. I have a couple of LargeSelect objects
> in the session storage. When these are loaded again, the object restarts
> the query thread. This fails, however, with a NullPointerException in
> TorqueInstance.getDB(). All data looks fine if I debug into the code. I
> suspect a race condition with the initialization of Torque but I'm not
sure.
>
> This behaviour is new with version 3.2 and probably tied to the new
> serialization/de-serializion code in LargeSelect.
>
> Anybody cares to comment? Scott?
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message