NAME
Apache::forks - Transparent Apache ithreads integration using forks
VERSION
This documentation describes version 0.022.
SYNOPSIS
# Configuration in httpd.conf
PerlModule Apache::forks # this should come before all other modules!Do NOT change anything in your scripts. The usage of this module is transparent.
DESCRIPTION
Transparent Apache ithreads integration using forks. This module enables the ithreads API to be used among multiple processes in a pre-forking Apache http environment.
REQUIRED MODULES
Devel::Required (0.07)
forks (0.26)
mod_perl (any)
Test::More (any)USAGE
The module should be loaded upon startup of the Apache daemon. You must be using at least Apache httpd 1.3.0 or 2.0 for this module to work correctly.
Add the following line to your httpd.conf:
PerlModule Apache::forksor the following to the first PerlRequire script (i.e. startup.pl):
use Apache::forks;It is very important to load this module before all other perl modules!
A common usage is to load the module in a startup file via the PerlRequire directive. See eg/startup.pl in this distribution. In this case, be sure that the module is first to load in the startup script, and that the PerlRequre directive to load the startup script is the first mod_perl directive in your httpd.conf file.
NOTES
threads->list and $thr->join differences in mod_perl
CGI scripts may behave differently when using forks with mod_perl, depending on how you have implemented threads in your scripts. This is frequently due to the difference in the thread group behavior: every mod_perl handler (process) is already a thread when your CGI starts executing, and all CGIs executing simultaneously on your Apache server are all part of the same application thread group. Your script is no longer executed as the main thread (Thread ID 0); it is just another child thread in the executing thread group.
This differs from pure CGI-style execution, where every CGI has its own unique thread group (isolated from all other Apache process handlers) and each CGI always begins execution as the main thread.
For example, if you were successfully doing the following in CGI:
use forks;
threads->new({'context' => 'scalar'}, sub {...}) for 1..5;
push @results, $_->join foreach threads->list(threads::running);the join operation would block indefinately in mod_perl until the current request handler timed out and the execution was terminated by Apache. This occurs because all other currently running Apache handler child processes are active perl threads that can not be joined until the Apache httpd server is shut down or the child handler is recycled by Apache (i.e. "/httpd.apache.org/docs/1.3/mod/core.html#maxrequestsperchild"" in <a href="http:MaxRequestsPerChild</a>> was exceeded).
The solution is to do the following instead:
use forks;
push @my_threads, threads->new({'context' => 'scalar'}, sub {...}) for 1..5;
push @results, $_->join foreach @my_threads;This insures join actions only occur on threads explicitly started by the script.
Additionally, never do the following in mod_perl:
threads->new({'context' => 'scalar'}, sub {...}) for 1..5;
$_->join foreach threads->list(threads::joinable); #<-- don't do thisas you might inadvertantly join threads started by from other Apache handler processes! Do the following instead:
push @my_threads, threads->new({'context' => 'scalar'}, sub {...}) for 1..5;
$_->join foreach map($_->is_joinable ? $_ : (), @my_threads);The good news about making such logic changes is that they will work both in CGI and mod_perl modes. If you code all your threaded CGIs in this style, your code should work fine without changes when switching to mod_perl.
TODO
Determine why mod_perl appears to skip END blocks of child threads (threads started in an apache-forked handler process) that complete and exit safely. This isn't necessarily harmful, but should be resolved to insure highest level of application and memory stability.
CAVIATS
This module will only work with Apache httpd 1.3.0 or newer. This is due to the lack of mod_perl support for PerlChildInitHandler directive. See "mod_perl" in mod_perl for more information regarding this.
For Apache 2.x, this module currently only supports the "/httpd.apache.org/docs/2.0/mod/prefork.html"" in <a href="http:prefork</a>> MPM (Multi-Processing Module). This is due to the architecture of forks, which only supports one perl thread per process.
BUGS
Forks 0.23 issues: Lots of warnings spew. DBI handles act unpredictably.
Forks 0.24 issues: Unstable handlers on some platforms, likely due to overloading %SIG. May need a less agressive signal management mode, for cases such as this.
CREDITS
- Apache::DBI
-
Provided the general framework to seamlessly load a module and execute a subroutine on init of each Apache child handler process for both Apache 1.3.x and 2.x.
AUTHOR
Eric Rybski
COPYRIGHT AND LICENSE
Copyright (c) 2007-2008 Eric Rybski <rybskej@yahoo.com>. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.