Jean-Frederic Clere commented on MODCLUSTER-398:
Actually the lock occurs in a piece of code that shouldn't be called in production (it
is just there for demos).
A fix that activates correctly the feature has been pushed
mod_cluster deadlock in a jboss/windows environment
Issue Type: Bug
Affects Versions: 1.2.6.Final
Environment: Windows 2008, EAP6 and EWS2.0.1
Reporter: Marc Maurer
Assignee: Jean-Frederic Clere
Under load Apache stops serving pages, with all threads are stuck in "W : Sending
reply" state. With the windows Process Explorer we then got a stacktrace from a
hanging thread. We don't have debug symbols, but it's easy enough to see
libapr-1.dll!apr_file_lock+0x69 <-- here
mod_slotmem.so+0x1318 <-- here
mod_manager.so+0x2a11 <-- here
So mod_manager is requesting a filelock on one of the lockfiles in in the MemManagerFile
path. In this case it was the "manager.sessionid.sessionid.lock" file. Removing
the lockfile fixed the problem.
When bisecting the mod_cluster code, I think commit
"74eeb9c026380deb8d833be53b09b3d808e02d10 - Lock in insert-update" in version
1.2.2 is the culprit. This would also explain why mod_cluster 1.2.1 is the last known
What we don't know, is which process is already holding the lock when all Apache
threads start blocking on it. We are trying to figure that out. There are no obviously
wrong lock/unlock slotmem call pairs in the mod_manager module, and no locks are requested
within other locks as far as we can see. Therefor our best guess would be a deadlock on a
thread already holding the globalmutex_lock in combination with the slotmem file locks,
but that's just a guess without debugging it.
More context can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=1080047
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira