On 2006-09-21 Michael Burns wrote: > I've recently upgraded one of our sites from Mason 1.28 to 1.33 and > discovered that these objects are not getting destroyed properly.
Hi, I can confirm that we have the same issue on using Mason with MasonX::Request::WithApacheSession and Apache::Session::MySQL. The session changes should get written to the DB at the end of the request. After upgrading Mason to 1.33 the writing of the session information to the DB is delayed for tens of seconds. It appears that $m is destroyed 30-90 seconds after the request has ended, which is really weird and causes the following requests to get old session information for a while. When the older session objects are really destructed the data does get to the DB. Downgrading back to 1.28 fixes the problem for now.. This appears to be a bug in the most recent version of HTML::Mason? ------------------------------------------------------------------------ Oskari "Okko" Ojala Frantic Media ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
