in reply to Re^2: Apache::Session problems under high load
in thread Apache::Session problems under high load

Perhaps you think in the wrong direction, the session is written when you untie the session. So if request 1 takes longer as request 2, r2 is written correct with locking, but is overwritten by request 1. assuming both use the same session_id
Boris
  • Comment on Re^3: Apache::Session problems under high load

Replies are listed 'Best First'.
Re^4: Apache::Session problems under high load
by Anonymous Monk on Oct 27, 2004 at 14:30 UTC
    We tried a hack to force flush to disk as early as possible but this broke everything so we stopped. We do try to untie as early as possible. Should I paste in the test scripts? They are a mess, admittedly, as they were thrown together from bits and pieces to prove a point.

    It really looks like locking really fails for us in the scripts.
[reply]
      I think even more that you think wrong on the locking issue. Try to add a Transaction => 1 to your tie, this is more likely what you want.
      Boris
[reply]
        That won't do much with MySQL.
[reply]

In Section Seekers of Perl Wisdom