Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#67 Sessions not waking up

closed-fixed
nobody
WebKit (58)
5
2004-04-02
2004-03-24
Aaron Switzer
No

I initially noticed that my sessions were timing out
even though they were being accessed throughout the
timeout period. After some testing I identified the
fact that session.awake() was not being executed.
After further investigation I realized that because
sessions are not created or retrieved until requested,
there is never a session stored in the transaction for
it to awake() during the transaction's own awake() cycle.

As a simple fix I have added
"session.awake(transaction)" in
application.createSessionForTransaction() after a
session is retrieved. Here is the diff output for the
modified Application.py:

312d311
< session.awake(transaction)

- Aaron Switzer

Discussion

  • Logged In: YES
    user_id=173690

    Upon investigation I found a few other problems in CVS;
    namely the Transaction.awake(), respond(), sleep() weren't
    being called at all, and therefore the session wasn't
    getting these calls either.

    It's all fixed and working now - thanks for the bug report!

     
    • status: open --> closed-fixed