https://issues.apache.org/bugzilla/show_bug.cgi?id=46763
Summary: Improve treatment of jk_log_lock.
Product: Tomcat Connectors
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: mod_jk
AssignedTo: dev@tomcat.apache.org
ReportedBy: mashm...@gmail.com
Created an attachment (id=23305)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=23305)
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. ).
regards.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
