I had the same problem. I boiled it down to Static::Simple. Each request to a static resource issued a session update. In a recent release of cat the handling of requests seemed to have changed. Try downgrading to 5.80018 which fixed it for me (which is not a good solution, but I have no time right know to fix it in catalyst or write a test).
On Tue, 27 Apr 2010 15:42:21 +0700, Ben van Staveren <[email protected]> wrote: > Hi folks, > > Recently after upgrading all of Catalyst, I'm witnessing some weird > behaviour in some apps. I'm using Catalyst::Plugin::Session::Store::DBIC > to store my sessions, and when I have DBIC_TRACE going, I see this: > > BEGIN WORK > SELECT me.id, me.session_data, me.expires FROM session me WHERE ( me.id > = ? ): 'session:fe3baeddb6ec2d3a14b07651a8792c7b85df9722' > COMMIT > UPDATE session SET expires = ? WHERE ( id = ? ): '1272443848', > 'session:fe3baeddb6ec2d3a14b07651a8792c7b85df9722 > > Not once per request, but up to 50 times in a single request. Is this > something wrong in my code or is C::P::S::S::DBIC going nuts? _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
