Bug 46763

Summary: Improve treatment of jk_log_lock.
Product: Tomcat Connectors Reporter: Eiji Takahashi <mashmk02>
Component: mod_jkAssignee: Tomcat Developers Mailing List <dev>
Severity: enhancement    
Priority: P2    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Attachments: patch for apache-2.0/mod_jk.c

Description Eiji Takahashi 2009-02-24 20:14:07 UTC
Created attachment 23305 [details]
patch for apache-2.0/mod_jk.c

Hi, folks.

If the graceful restart occurs, jk_log_lock that an old child process has is deleted by the parent process and the new one is made.
When an old child process writes the request log after the parent process restarted, the following logs are written in error_log 
because old jk_log_lock has already been deleted. 
# An old child process doesn't stop until the reply is returned.

[Mon Feb 16 14:38:57 2009] [error] (22)Invalid argument: apr_global_mutex_lock(jk_log_lock) failed
[Mon Feb 16 14:38:57 2009] [error] (43)Identifier removed: apr_global_mutex_unlock(jk_log_lock) failed

To avoid output logs, I modified the code to reuse jk_log_lock by using apr_pool_userdata_set/get() ( just like other modules. for instance, mod_ssl etc. ).

Comment 1 Mladen Turk 2009-02-24 23:32:19 UTC
Applied to the trunk.
Comment 2 Mladen Turk 2009-12-20 23:50:54 UTC
Closing this issue