quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Lehuen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (MODPYTHON-35) mod_python.c doesn't always log reason for 500 error
Date Thu, 17 Mar 2005 20:48:20 GMT
     [ http://issues.apache.org/jira/browse/MODPYTHON-35?page=history ]
Nicolas Lehuen resolved MODPYTHON-35:

      Assign To: Nicolas Lehuen
     Resolution: Fixed
    Fix Version: 3.2.0

Fixed as mentionned in the mailing list. I've added a few check for NULL values where formatted
string are used.

> mod_python.c doesn't always log reason for 500 error
> ----------------------------------------------------
>          Key: MODPYTHON-35
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-35
>      Project: mod_python
>         Type: Improvement
>   Components: core
>     Versions: 3.1.4
>     Reporter: Graham Dumpleton
>     Assignee: Nicolas Lehuen
>     Priority: Minor
>      Fix For: 3.2.0

> In src/mod_python.c, there is code in various places of the form:
>     /* get/create interpreter */
>     idata = get_interpreter(interp_name, req->server);
>     if (!idata)
> Ie., 500 errors is returned for a quite serious problem.
> If one looks in get_interpreter() though, when it returns a NULL,
> it doesn't always log why.
> Now one would hope that it would never fail in the first place, but
> it is failing on Mac OS X when "restart" and not "stop/start" is used
> by some people. The lack of logged messages has mean't some
> detective work to localise the problem. The actual cause is still
> being sort, but comprehensive logging in get_interpreter() is
> worthy of a request in itself.
> For further information see mailing list thread of which the following
> is a part.
>   http://www.modpython.org/pipermail/mod_python/2005-March/017661.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message