[
https://issues.apache.org/jira/browse/MODPYTHON-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Graham Dumpleton reopened MODPYTHON-195:
----------------------------------------
The change for this appears to be having the side affect of the
mod_python/Python version information not showing up in the Apache startup
string. This is based on logging shown in email:
http://www.modpython.org/pipermail/mod_python/2007-May/023582.html
Where would would expect to see something like:
Apache/2.2.4 (Win32) mod_python/3.3.1 Python/2.5 PHP/5.2.1 configured --
resuming normal operations
on Windows one is only seeing:
Apache/2.2.4 (Win32) PHP/5.2.1
This is because the version information is output in the first Windows process
created, but the change is stopping the code which composes the version
information from being run.
The code should be reorganised so that calls to ap_add_version_component() for
mod_python and Python are always done. When done second time it is redundant
but doesn't matter.
> Possible leaking of Win32 event handles when Apache restarted.
> --------------------------------------------------------------
>
> Key: MODPYTHON-195
> URL: https://issues.apache.org/jira/browse/MODPYTHON-195
> Project: mod_python
> Issue Type: Bug
> Components: core
> Affects Versions: 3.2.10
> Reporter: Graham Dumpleton
> Assigned To: Graham Dumpleton
> Fix For: 3.3
>
>
> Jeff Robins in:
>
> http://mail-archives.apache.org/mod_mbox/httpd-python-dev/200610.mbox/[EMAIL
> PROTECTED]
> indicates a belief that when an Apache restart is performed on Windows that
> there are a number of Win32 event handles leaked. His belief is that this
> seems to be linked to mod_python.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
