Foo JH wrote:
> William A. Rowe, Jr. wrote:
>> Foo JH wrote:
>>
>>> Yes! It's really (in)famous! :) The more detailed error message seems to
>>> be captured in the Event Application log instead. I wonder why error.log
>>> wasn't more verbose on this one.
>>
>> Because, once it crashes it's no lon
CC-ing to [EMAIL PROTECTED] in the hopes that someone (**cough**wrowe?**cough**)
might shed some deeper insight into why things were/are done the way
they are, and what, if anything, would be needed to be done to make
things better.
I don't think that the problem is mod_perl, as much as the wi
Issac Goldstand wrote:
> CC-ing to [EMAIL PROTECTED] in the hopes that someone
> (**cough**wrowe?**cough**)
> might shed some deeper insight into why things were/are done the way
> they are, and what, if anything, would be needed to be done to make
> things better.
>
> I don't think that the prob
Philip M. Gollucci wrote:
Its been about 6 years since I've tried anything mod_perl windows
related, but I recall that some of the startup.pl files of that time
loaded LibXML and related by default. You might have been loading it and
just not using it.
The related problem on windows is that m
Philip M. Gollucci wrote:
> William A. Rowe, Jr. wrote:
>> Keep in mind, using the official build of httpd you have .pdb debug
>> files that can be downloaded that exactly match the .exe/.dll's/.so's
>> that we ship. That means you can -debug- these segfaults.
> Am I able to make these from UNIX ?
Issac Goldstand wrote:
I don't think that the problem is mod_perl, as much as the winnt MPM in
Apache2. The bottom line is that if anything goes wrong, you need the
singleton child process to recycle itself, and very often in the case of
mod_perl that can take a long time.
There is experim
William A. Rowe, Jr. wrote:
Keep in mind, using the official build of httpd you have .pdb debug
files that can be downloaded that exactly match the .exe/.dll's/.so's
that we ship. That means you can -debug- these segfaults.
Am I able to make these from UNIX ?
Where can I read about this?
Randy
Foo JH wrote:
>
> By 'bad code' you're referring to code written by app developers? I
> suspected I fall into that category, but even when I throw in all the
> eval traps, the .dll errors still come to crash (and automatically
> restart) apache.
By bad code, I mean flaws in apr, httpd, modperl, p
Hey Stephane,
Thanks for zeroing in on the problem libraries. I don't remember using
LibXML, but I'll see if I can replicate the problem as well, in a
simplified model.
Stephane GUIBOUD-RIBAUD wrote:
I had a similar issue one year ago with mod_perl 2.0.0-RC4 and perl
5.6.1 (same issue with p
William A. Rowe, Jr. wrote:
Foo JH wrote:
Yes! It's really (in)famous! :) The more detailed error message seems to
be captured in the Event Application log instead. I wonder why error.log
wasn't more verbose on this one.
Because, once it crashes it's no longer logging?
Yet it is abl
In the list of all modules you are using in your application, are you
sure that all modules are thread-safe ? If only one is not
thread-safe, you may encounter an error at a time while running your
application ?
For my part, I use mainly CPAN libraries. This includes:
HTML::Template
DBI
DBD::
Henrik Schak Hansen wrote:
Hi All,
I think we are a lot of windows users experiencing the same problem with mod_perl/apache:
"The famous 3221225477 exit status".
My company will also be willing to donate some money If it will help solving
the problem.
Yes! It's really (in)famous! :) The more d
I had a similar issue one year ago with mod_perl 2.0.0-RC4 and perl
5.6.1 (same issue with perl 5.8).
The problem was due to the use of LibXML (which is the fastest xml
parsing library I found to parse large XML files) with mod_perl and
apache in a multi-threaded environment. I also had some i
Foo JH wrote:
> Yes! It's really (in)famous! :) The more detailed error message seems to
> be captured in the Event Application log instead. I wonder why error.log
> wasn't more verbose on this one.
Because, once it crashes it's no longer logging?
We were originally using 5.8.3, but reproduced the problem with both
activeperl 5.8.8.819 with mod_perl-2.0.3-dev (from your PPM repository)
as well as our own built perl + mod_perl 2.0.3-rc2
Randy Kobes wrote:
> On Sun, 19 Nov 2006, Foo JH wrote:
>
>> Issac Goldstand wrote:
>>> YES! While it's
On Sun, 19 Nov 2006, Foo JH wrote:
Issac Goldstand wrote:
YES! While it's acceptable for light and smallish applications, I've never
found it to be really usable once you're serving concurrent connections.
On that note, I have a contract (job) offer for anyone who knows their way
inside Per
This is a disappointing piece of news. Perl itself is very useful on the
Windows environment. If modperl cannot be reliably deployed on Windows,
how can we expect the Windows developers (which form the majority of
developers) to consider adopting perl/ modperl for the enterprise?
I hope we can
Why don't you post the error message here, and see if anyone has seen it
before?
Issac Goldstand wrote:
YES! While it's acceptable for light and smallish applications, I've
never found it to be really usable once you're serving concurrent
connections.
On that note, I have a contract (job) o
YES! While it's acceptable for light and smallish applications, I've
never found it to be really usable once you're serving concurrent
connections.
On that note, I have a contract (job) offer for anyone who knows their
way inside Perl (5.8) and mod_perl (2) enough to help troubleshoot a
win
19 matches
Mail list logo
