Without PR number, it seemed too hard to point out the changed code source code.
So I wished that there appear specific PR number from some root "Change Log"
data.
> Not as such. Check the SVN record for the context of the changes that
> introduced each of those. Or tell us what problem you're trying to solve
> and maybe we can tell you something specific.
All right.
Since I am new to Apache development community, I would like to start from
checking "SVN" and "SVN record" to ensure if we can identify the relationship
with the four Change Log entries.
By the way, our original problem was the side effect of
SIGUSR1 handling change of Worker MPM for our custom module.
For mission critical module, unexpected SIGUSR1 caused service stop.
And we already resolved the problem.
Line 1534, Version 2.2.3, module, worker
Description:
*) Worker MPM: On graceless shutdown or restart, send signals to
each worker thread to wake them up if they're polling on a
Keep-Alive connection. PR 38737. [Chris Darroch]
We felt very sorry when we found no suggestion of that change
in the Apache 2.2 migration document. This kind of change
for inter module I/F can cause unexpected behavior of custom module.
--
Regards,
Tetsuo.
Full name Tetsuo Kuge Hewlett-Packard Japan, Ltd.
E-mail tetsuo.k...@hp.com
