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 switche
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
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 se
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
source code that is being modified and copied to the children.
Thanks for your help,
Malte Ubl
--
SCHAFFHAUSEN COMMUNICATION GROUP
Schaffhausen Advertising GmbH / Daimlerstraße 17 / 25337 Elmshorn
Fon +49 41 21.47 29-459 / Fax +49 41 21.47 29-455
[EMAIL PROTECTED] / www.schaffhausen.de
repeat the whole testing phase.
Thank You!
Malte Ubl
--
SCHAFFHAUSEN COMMUNICATION GROUP
Schaffhausen Advertising GmbH / Daimlerstraße 17 / 25337 Elmshorn
Fon +49 41 21.47 29-459 / Fax +49 41 21.47 29-455
[EMAIL PROTECTED] / www.schaffhausen.de
