Re: [ANNOUNCE] mod_perl 2.0.5
I have finally started testing mod_perl-2.0.5 on windows (both win 2003 / 2008). I compiled mod_perl using Visual Studio 2010 Express, Perl 5.10.1, and Apache 2.2.19. The reason that I wanted to use 2.0.5 of mod_perl was to resolve the issue with the Apache Process stopping. This was the original issue that I was able to repeat with 2.0.4 - http://www.gossamer-threads.com/lists/modperl/dev/102357 >From my testing, I still can stop the Apache process by stopping the browser in a middle of a connection. I used to have APR does not understand... Now, I have this error (instead of the APR error): ModPerl::Util::exit: (12) exit was called at D:/InterfaceServer/Perl/lib/CGI/Carp.pm line 561 Parent: child process exited with status 255 -- Restarting. We are going in the right direction, just need to figure out how to solve this new issue. Does anyone have any ideas on how to fix this? Thanks, as always. Hans On Wed, Feb 9, 2011 at 10:22 PM, Randolf Richardson wrote: > > Awesome everyone. Thanks for working on the new release of mod_perl. I > look > > forward to implementing it. > > This is great news! I'm very pleased to see this update because it > flies in the face of those who incorrectly insist that ModPerl is > dead because it hasn't been updated for a long time -- I've been > pointing out that the lack of updates are due to better quality code > and fewer change requirements. > >Thanks too all developers and contributors of ModPerl! I've been > hooked on this technology ever since I started using it, and I enjoy > the high performance and deep integration into APR and HTTPd. > > > Has anyone tried 2.0.5 on Windows? > > I haven't yet, but I look forward to trying it on NetBSD 5.1. I am > interested in trying it on Windows when a binary is available... > >I find that running ModPerl on Windows generally works well until > Perl scripts are changed frequently (and using the Reload module), > and then Apache HTTPd will either stop responding or just crash out > (especially if PerlMagick is in the mix). I wonder if this might be > an OS-specific problem thought since my Unix servers just don't > exhibit these symptoms. > > [End of reply.] > > > On Wed, Feb 9, 2011 at 6:12 PM, Jie wrote: > > > > > Thank you so much for the new release! > > > > > > Jie > > > > > > Please think of our environment and only print this e-mail if > necessary. > > > > > > * Andr? Warnier wrote: > > > > > > > Date: Tue, 08 Feb 2011 09:18:33 +0100 > > > > From: Andr? Warnier > > > > To: mod_perl Dev > > > > CC: mod_perl list > > > > Subject: Re: [ANNOUNCE] mod_perl 2.0.5 > > > > User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) > > > > > > > > Many thanks guys, for keeping mod_perl alive and well (and perl too > for > > > that matter). > > > > It is really a pity that not more people know how much their nice > > > > web applications depend on it. > > > > But then, maybe we should think that the people who matter, do know. > > > > > > > > > > > > Randolf Richardson - rand...@inter-corporate.com > Inter-Corporate Computer & Network Services, Inc. > Vancouver, British Columbia, Canada > http://www.inter-corporate.com > > >
Same script with different locations
Folks, I wanted to know if there was anything wrong with using the same MP2 content handler with multiple Location directives in apache and using $r->location() to determine the script that should be used in forms, redirects etc. We have someone that insists in having different URL's doing something pretty specific while 75% of everything else is share (auth, profiles etc). It seems to work fine, whatever URL you come in on you will stay on, but there is just something about doing it that made me want to ask. TIA!
Re: Same script with different locations
On Sunday, May 29, 2011 19:40:59 cfaust-dougot wrote: > I wanted to know if there was anything wrong with using the same MP2 > content handler with multiple Location directives in apache and using > $r->location() to determine the script that should be used in forms, > redirects etc. Nothing wrong with it. But be careful, the administrator can try to configure it like: or I am not 100% sure but I think $r->location will contain "(something| special)/" in that case. Torsten Förtsch -- Need professional modperl support? Hire me! (http://foertsch.name) Like fantasy? http://kabatinte.net
Re: [ANNOUNCE] mod_perl 2.0.5
Hans, > ModPerl::Util::exit: (12) exit was called at > D:/InterfaceServer/Perl/lib/CGI/Carp.pm line 561 > Parent: child process exited with status 255 -- Restarting. I have done a lot of testing on windows with the 2.05 release and have not seen this error before. It must be something specific in your code. It looks like the exit command is triggers some where in your code ( http://perl.apache.org/docs/2.0/api/ModPerl/Util.html#C_exit_ ). Does it also restart Apache? I have done some testing with calling ModPerl::Util::exit(0) (that's what is actually done in CGI::Carp) and did not found an error in my log. does it say [error] or [warn] in your log file ? -- Thomas
Re: [ANNOUNCE] mod_perl 2.0.5
Yes, the entire process restarts. Here is the exact line: ModPerl::Util::exit: (12) exit was called at D:/InterfaceServer/Perl/lib/CGI/Carp.pm line 561 [Sun May 29 05:25:10 2011] [notice] Parent: child process exited with status 255 -- Restarting. It's a notice. I did some further testing and found that it restarts and exits apache when the application is printing to the browser. So, if you have a bunch of data to send to the browser and the connection stops in the middle, it throws the above error. my $template = "Lots of data .."; print $template; Is there a better way to transfer lots of data to the browser? This is where I was able to to track it down to. If I stop the browser before it hits this print line, the "ModPerl::Util::exit(0)" works. Thanks fro taking a look. Hans On Sun, May 29, 2011 at 3:07 PM, Thomas den Braber wrote: > Hans, > > > ModPerl::Util::exit: (12) exit was called at > > D:/InterfaceServer/Perl/lib/CGI/Carp.pm line 561 > > Parent: child process exited with status 255 -- Restarting. > > I have done a lot of testing on windows with the 2.05 release and have not > seen this error before. It must be something specific in your code. It > looks like the exit command is triggers some where in your code ( > http://perl.apache.org/docs/2.0/api/ModPerl/Util.html#C_exit_ ). > > Does it also restart Apache? > > I have done some testing with calling ModPerl::Util::exit(0) (that's what > is actually done in CGI::Carp) and did not found an error in my log. does > it say [error] or [warn] in your log file ? > > -- > Thomas > > >
Re: Same script with different locations
Torsten Förtsch wrote: On Sunday, May 29, 2011 19:40:59 cfaust-dougot wrote: I wanted to know if there was anything wrong with using the same MP2 content handler with multiple Location directives in apache and using $r->location() to determine the script that should be used in forms, redirects etc. Nothing wrong with it. But be careful, the administrator can try to configure it like: or I am not 100% sure but I think $r->location will contain "(something| special)/" in that case. It does, I can confirm. I had a case today, with something like this : SetHandler modperl PerlResponseHandler blabla .. and in the handler, with $r->location, I got something like "\\.thtm$" $r->filename on the other hand gave the full *path* (on disk).
