Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of henri.gomez@gmail.com
 designates 64.233.162.233 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Jk5Og65O+6OaneLa/ixwDZSY5MenzdpMGSAOzL7dA1setfmRMabCE3CVVEjCWKEq93FfwjLca3EgZWR6jJF51SP7CI4yeiOwywhQQBjZB/DxKmykXBaVI88RehYq3FMjtTyNQ8xIF5ztToDYgP5vtEE3jLYXSVtYKfkwalh5diM=
Message-ID: <6291fc850704240615s6b0d9093xccc287e176aa87fd@mail.gmail.com>
Date: Tue, 24 Apr 2007 15:15:56 +0200
From: "Henri Gomez" <henri.gomez@gmail.com>
To: "Tomcat Developers List" <dev@tomcat.apache.org>
Subject: Re: More on i5/OS and some modifications needed
In-Reply-To: <462E0258.4080406@kippdata.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3iGbeK7K29xXqpTGf302BA6QWrBhemCTbwRoOY5aUrS@akmail>
	 <6291fc850704230744n677f6e83i37d87d6aeab4b4a7@mail.gmail.com>
	 <n7iuDbvSOXmj0rhstDr6lnBWbYZbu08PnzbswtGKmR8@akmail>
	 <dcBhHsJpcfDApt4rcmVpcozLJq2NHTdUShiohjzv2He@akmail>
	 <6291fc850704231508o7b5bd5eaofb4942ceec3a48e8@mail.gmail.com>
	 <6291fc850704240201m6e076c9chdb849efd36e8d9ba@mail.gmail.com>
	 <462DCFCF.2040405@kippdata.de>
	 <6291fc850704240321y70a6651bo31c6b10b1e7395d2@mail.gmail.com>
	 <6291fc850704240537h33f6b619yf9964a4101caefcd@mail.gmail.com>
	 <462E0258.4080406@kippdata.de>

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 <rainer.jung@kippdata.de>:
> 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: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org