Hi,

I guess the problem might happen when the same child serves the page 
again, so the initialisation is skiped.

Could you try to run httpd with the -X option, so you have only one 
process. Does it now fail the second request?

Gerald


------------------------------------------------------------------------
--
Gerald Richter       ECOS electronic communication services GmbH
*******************  SECURING YOUR NETWORK  ********************

Post:       Tulpenstrasse 5            D-55276 Dienheim b. Mainz
E-Mail:     [EMAIL PROTECTED]            Voice:   +49 6133 939-122
WWW:        http://www.BB-5000.info    Fax:     +49 6133 939-333

Sitz der Gesellschaft: Dienheim; AG Mainz HRB 6889; GF: W.Heck, 
G.Richter
------------------------------------------------------------------------
--
 
  

> -----Original Message-----
> From: Ben Kim [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, May 31, 2007 12:34 PM
> To: embperl@perl.apache.org
> Subject: error document
> 
> 
> Hi,
> 
> I reported a related problem once but didn't get a good 
> answer last time... I thought I'd try again.
> 
> We are on
> Apache/2.2.4 Embperl 2.2.0 mod_perl/2.0.3 but not using 
> Embperl Objects.
> 
> I'm trying to solve the problem of 500 errors not showing 
> custom error document, after the server is accessed a couple 
> times. If I gracefully restart the apache, it shows correct 
> error document a couple times. Then, after that, anything 
> that causes 404 will show embperl's own 500 page, not my custom page.
> 
> This happens only for pages that have file extensions handled 
> by embperl.
> If I have <FilesMatch ".*\.epl$|.*\.html">, .htm just behaves 
> as expected. 
> (custom error page shows, regardless of how many times I try.)
> 
> I have both
> optReturnError = 262144
> optRedirectStdout = 16384
> 
> PerlSetEnv EMBPERL_OPTIONS 278528
> PerlSetEnv EMBPERL_DEBUG 10477
> 
> The log shows difference between the two.
> 
> Log entries for initial accesses (custom page is shown) 
> ====================
> 
> On initial access to custom error pages, the error in embperl 
> log is as
> follows:
> 
> [30133]REQ: ***** Start Request at Tue May 29 13:23:12 2007 
> [30133]Use App: Embperl [30133]Formdata... length = 0 
> [30133]Using APACHE for output...
> [989] Use Recipe Embperl
> [989]SYNTAX: switch to Embperl::Syntax::Embperl 
> [30133]Reading [snip]/testke.epl as input using PerlIO (0 Bytes)...
> [30133]ERR:  404: testke.epl(1): Not found 
> '[snip]/testke.epl',   searched: No 
> such file or directory
> ...
> [30133]REQ: ***** Start Request at Tue May 29 13:23:12 2007 
> [30133]Use App: Embperl [30133]Formdata... length = 0 
> [30133]Using APACHE for output...
> [989] Use Recipe Embperl
> [989]SYNTAX: switch to Embperl::Syntax::Embperl 
> [30133]Reading [snip]/500.epl as input using PerlIO (643 Bytes)...
> ...
> [30133]Request finished. Tue May 29 13:23:12 2007
> 
> 
> Log entries thereafter  (custom page is not shown) 
> ======================
> [987]SYNTAX: switch to Embperl::Syntax::Embperl
> [30133]ERR:  404: testkke.epl(1): Not found 
> '[snip]/testkke.epl', searched: No such file or directory
> 
> or [947]SYNTAX: switch to Embperl::Syntax::Embperl
> [30133]ERR:  24:  Error in Perl code: Died at
> [snip]/teste.epl    line 2.
> 
> 
> As you see, the log entries are quite short (just two lines) 
> for subsequent accesses. The PerlIO line is gone.
> 
> This is a problem for me since all 404 errors are showing 
> this not so pretty error page. Is this only for me? Is anyone 
> willing to share a working configuration?
> 
> 
> Thanks.
> 
> Ben K.
> Developer
> http://benix.tamu.edu
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ** Virus checked by BB-5000 Mailfilter ** 
> !DSPAM:416,465ea702112691079068920!
> 
> 

** Virus checked by BB-5000 Mailfilter **

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to