Re: how to trap connection reset/abort in Apache::Filter?

[prev] [thread] [next] [Date index for 2005/05/12]

Jeff Ambrosino wrote:
> Ok, this is going to be tough for me to test because I'm still on RC4,
> so it's not yet converted to the new Apache2 naming.  I'll still try
> to make/test the svn snapshot, though (which also gives me a good
> reason to get more familiar with subversion.)  I'll email what I find
> out.
> 
> thanks Stas!

OK, may be just try comparing to:

   $@ == APR::Const::ECONNABORTED or $@ == APR::Const::ECONNRESET

The new subs just supposed to work on more platforms, where other similar 
codes may be sent by the system.

You can still play with the test t/protocol/TestProtocol/echo_nonblock.pm 
from RC4.

but looking again at your report, I can see that the issue is elsewhere.

I believe it's coming from src/modules/perl/modperl_filter.c:

     if (filter->mode == MP_INPUT_FILTER_MODE) {
       ...
     }
     else {
         MP_RUN_CROAK(modperl_output_filter_flush(filter),
                      "Apache2::Filter");
     }

is that it? if you change the "Apache2::Filter" string (drop the 2 in your 
case) to something else?

        -- 
        __________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@xxxxxx.xxx http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com