Re: Apache::Session::MySQL, light/heavy proxy, wedging

[Todd Finney <suppressed>]

At 05:52 PM 1/30/2007 -0500, Jonathan Vanasco wrote:
> my gut feeling is that you're having an error that deals with valid /
> invalid / new session ids.  but it could really be anything - maybe
> you're having connectivity issues with apache::session (timing out ?
> are you using apache::dbi ? etc )

The bigger, fancier test case checks all of that.

----
       my %session = ();
        $log->info("AccessManagement::Session: tying session");
        eval {
            tie %session, 'Apache::Session::MySQL',$session_id, {
                DataSource=>'dbi:mysql:boygenius',
                UserName=>'nobody',
                Password=>'XXXXXXXX',
                LockDataSource=>'dbi:mysql:boygenius',
                LockUserName=>'nobody',
                LockPassword=>'XXXXXXXX',
            };
        };
        if ($@) {
            $log->info('AccessManagement::Session: '.$@);
            undef $session_id;
            tie %session, 'Apache::Session::MySQL',$session_id, {
                DataSource=>'dbi:mysql:boygenius',
                UserName=>'nobody',
                Password=>'XXXXXXXX',
                LockDataSource=>'dbi:mysql:boygenius',
                LockUserName=>'nobody',
                LockPassword=>'XXXXXXXX',
            };
            $log->info('AccessManagement::Session: New Session Created 
Successfully.');
        }
        $log->info('AccessManagement::Session: session id: '.$session_id);

----

It wedges at "AccessManagement::Session: tying session"

What I posted was a simplified test case, in order to demonstrate the 
problem in as few lines of code as possible.  I even used as a base a code 
section that should be "known good", as it appears in the perldoc for the 
manual.  I thought that I made this pretty clear, I'll try harder next time.

Problems such as Apache::Session timing out are unlikely to be the culprit, 
as the problem is reliably reproducible under narrow, specific 
circumstances as outlined in my original message.  Sessions created under 
the successful cases never fail, and sessions created under the failure 
cases never succeed.  Removing the single line in question causes all 
requests to succeed.

> just as an example, in my session class i do:

Yea, thanks.

> anyways, you shouldn't be writing new code for 1.3.x  unless you're
> stuck supporting a legacy app.

And thanks again.