I made it works by adding main_log = NULL in jklog_cleanup
static apr_status_t jklog_cleanup(void *d)
{
/* set the main_log to NULL */
d = NULL;
main_log = NULL;
return APR_SUCCESS;
}
Don't forget that jk is initialized twice and on i5/OS in the same
thread, so may be the static var should be reset.
What do you think of the patch ?
2007/4/24, Rainer Jung <[EMAIL PROTECTED]>:
main_log is a static in mod_jk.c, which is initialized as NULL.
It gets set inside open_jklog() which gets called once for every virtual
server by jk_post_config() during server initialization.
The first virtual server inherits its logger conf->log from its
configuration to main_log. It also registers a cleanup handler which
will NULL its conf->log, but that should not change main_log.
main_log should never get reset.
To find the problem, it would be best to first reduce the apache config
to not use any virtual servers.
You can log the value of main_log for debug purposes anywhere in
mod_jk.c, because its a global static.
Regards,
Rainer
Henri Gomez schrieb:
> I'm looking for the exception in jk_log. It happen in ws_write right
> now and I wonder what's the life cycle of main_log.
>
> On i5/OS, the init / post are done on the same thread (not the same on
> Unixes).
>
> How is reset the main_log ?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
