On 1/30/07, Todd Finney <[EMAIL PROTECTED]> wrote:
- When I fire up a new browser and access http://192.168.0.4/, the browser hangs. In my bigger fancier handler with more detailed logging, it seems to hang right before the session tie.
Any time that Apache::Session hangs, it's because of the excusive locking that it does. It tries to get a lock when you call tie(), and if another session object with the same ID is already holding that lock, it will hang. A glance at your problem description makes it sound like there could be internal redirects happening, while the parent request holds onto its session and lock, causing a hang. Before I spend too much time analyzing your symptoms, are you sure that your application requires excusive locks on sessions? If not, you can use Apache::Session::Lock::Null for your locking class. You will not get any data corruption because MySQL already insures that updates are atomic. The difference is that without exclusive locks you can get lost updates if a user tries to modify a session from two separate requests simultaneously. (Not usually an issue, but it can be for certain kinds of applications.) - Perrin
