On Tue, 2004-05-11 at 16:51, sagi wrote: > Perl version 5.005_03 That's pretty old. You should seriously consider going to 5.6.1 or later when you can.
> things start to go wrong. IE, data is not all there which gives > errors, die statement, warnings. All sorts of bad stuff, but when > hitting refresh it seems to work. This is not a very helpful error report. Can you describe exactly what happens? Show us messages from the error_log? Show us code? > I suspect either there is a closure somewhere, or possibly when a > child dies, the session ID terminates? If the session ID is stored in the database, it should not be lost when a child process dies. > And I canʼt really test this in single mode because of the load. No one would suggest you run in single mode on your production server. You do that on your test server, where there is no load. > Can I use some module to make sure the session ID doesnʼt terminate > per child, or am I barking up the wrong tree here? Probably the wrong tree. > As of now, I disabled mod_perl, but things are very very slow When you run it under CGI you don't see any of these errors? That would point to a problem with a global variable or closure. - Perrin -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
