I've been porting a Mason App from Apache 1.3.x & mod_perl 1.x to Apache 2.0.x and mod_perl 2.0.1.
HTML::Mason is 1.35 Apache::Session is 1.82 I ran into problems with Apache::Session::File because of locking problems. I can't really provide too many details other than every second request in the same session hung in a wait state forever. So I read about the Netdisco folks switching over the Apache::Session::Postgres and fgured I'd give it a try. Now, Sessions work, but _every_ request creates a new session. Meaning my app is completely broken. Am I missing something: PerlSetVar MasonRequestClass MasonX::Request::WithApacheSession PerlSetVar MasonSessionClass Apache::Session::Postgres PerlSetVar MasonSessionUseCookie 1 PerlSetVar MasonSessionCommit 1 PerlSetVar MasonSessionDataSource dbi:Pg:database=sessions PerlSetVar MasonSessionUserName session_user PerlSetVar MasonArgsMethod mod_perl I'm glad that all my Mason Code is running perfectly in mod_perl 2.0 save this session problem. Also, I'm seeing that I have pgsql processes "idle in transaction". Is there something I should be calling at the of my autohandler to force the session to commit? -- Brad Lhotsky ------------------------------------------------------------------------- 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
