Hi,
I'd really appreciate some help with a really weird mod_perl problem we
keep running into.
This is mod_perl version 1.29 using Apache::PerlRun
The application servers of our mod_perl site occasionally (once every
2-3 weeks) start spitting out these error messages:
[Sun Jul 3 14:58:0
Malte Ubl wrote:
Hi,
I'd really appreciate some help with a really weird mod_perl problem we
keep running into.
This is mod_perl version 1.29 using Apache::PerlRun
The application servers of our mod_perl site occasionally (once every
2-3 weeks) start spitting out these error messages:
[
Stas Bekman wrote:
The application servers of our mod_perl site occasionally (once every
2-3 weeks) start spitting out these error messages:
[Sun Jul 3 14:58:01 2005] [error] Modification of a read-only value
attempted at
/usr/local/lib/perl5/site_perl/5.8.6/i686-linux/Apache/PerlRun.pm lin
Malte Ubl wrote:
Can you reproduce the problem at will?
Unfortunately not. Although I have seen the problem on our development
system (where I was testing), the problem is not reproducable. As I said
the live system doesn't behave deterministically either. The conditions
under which is fail
Stas Bekman wrote:
Malte Ubl wrote:
Can you reproduce the problem at will?
Unfortunately not. Although I have seen the problem on our development
system (where I was testing), the problem is not reproducable. As I
said the live system doesn't behave deterministically either. The
condition
Malte Ubl wrote:
[...]
Our code is not using any specials variables though except %SIG for
alarm.
I've used $$ just as an example, any variable can be affected.
How does a variable become read-only? Is that something that can be done
on C/XS Level?
Yes. By setting the READONLY flag on the
Stas Bekman wrote:
Malte Ubl wrote:
[...]
Our code is not using any specials variables though except %SIG for
alarm.
I've used $$ just as an example, any variable can be affected.
How does a variable become read-only? Is that something that can be
done on C/XS Level?
Yes. By setting
Malte Ubl wrote:
[...]
We made this test on the production system where the error seems to
occur on about 50% of the occassions described in my older mails.
We introduced a #line statement which gives conclusive results pointing
to this line in PerlRun.pm:
$pr->{'code'} = $pr->{r}->slurp_file
Stas Bekman wrote:
Could this error occur if the close or unlock a type glob that does
not have a file handle in it?
May be. It's hard to tell w/o being able to reproduce the problem.
Another thing to try is to change the perl source code to dump the sv:
sv_dump(sv);
in the place it logs
Malte Ubl wrote:
Server stops working and spits out Modification of read only value
errors
We'll try moving to Apache::Registry first. As far as I can see
Apache::Registry should call slurp_filename less often (only once per
child and modification time).
For the record: We switched the produ
10 matches
Mail list logo
