On Tue, Mar 3, 2009 at 12:27 PM, Ben Bangert <[email protected]> wrote: > On Mar 3, 2009, at 12:24 PM, Mike Orr wrote: > >>>>> Â fcntl.flock(filedescriptor, fcntl.LOCK_EX) >>> >>> TypeError: argument must be an int, or have a fileno() method. >> >> Nobody knows about this? > > I don't, no. Mike Bayer might. Can you try upgrading Beaker just to ensure > it wasn't fixed? How do you reproduce?
I can't reproduce it on demand. It happened about 6 times this morning between 8 and 9 AM, and once in the last hour. This on a site that gets an average of 26 requests a minute, so it happens in occasional spurts. It started after I began using session.id in a function call in the base controller. I upgraded to Beaker 1.2.3 and Pylons 0.9.7 (from 1.1.2 and 0.9.7rc4), so I guess I'll know tomorrow if that fixes it. Is it efficient to use session.id in all requests, even those that don't otherwise use or modify a session? Would that in itself create a persistent session object? Is there a way to get the session ID if a session has been established for this request, or None if not? Because another problem I'm having is that certain requests (all related to RoboHelp static files, which are served by paste.fileapp and requested by RoboHelp's Javascript) are being logged with a different session ID for every hit, which ruins the aggregate session count. One site contains only RoboHelp files and is doing this throughout. Another site uses RoboHelp only for its help section, and the problem seems to be isolated to that section. So I could blame the browser or Javascript, but isn't Beaker generating the session ID? What criteria does it use to determine whether to generate a new ID? Would it be typical for Javascript requests to not send the session cookie, or does the browser just send them automatically? -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
