Dec 16, 2009, 5:18 PM
Post #7 of 11
Interesting, but it's _not_ a scoping issue. I understand scope, very well. The problem, as I said, was somehow that Linux, or the version of Perl my server's are running under prod are caching the "my" vars (at least the ones that are in the _outer_ scope) between invocations. I found that if I re-invoked the app within a few seconds (anywhere between 0-15s) I would get the "odd" behavior. If, however, I waited somewhere more than 15s, then I would get "correct" behavior.
Re: [FishMonger] Unix - Thread issue?
[In reply to]
I found if I was somehow able to gen two requests simultaneously, the first would fail and the 2nd would be OK. This led me to believe it was some kind of weird "caching" behavior in the thread inside the server under Linux. It was baffling to me how it happened. I could probably reduce it to a very simple set of sample code now that I understand the issue.
I'd be happy to do that, only, it probably would only show the error on the servers I was using. Maybe...