httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34288] New: - thread spinning on apr_thread_mutex_lock in apache 2.0.53
Date Mon, 04 Apr 2005 13:47:54 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34288>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34288

           Summary: thread spinning on apr_thread_mutex_lock in apache
                    2.0.53
           Product: Apache httpd-2.0
           Version: 2.0.53
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: amudev@amuel.net


Threads in Apache 2.0.53 locks up the cpu sometimes. I never saw this in 2.0.52.
I am using the worker mpm on linux 2.6, Debian Sarge with ssl enabled.

Server status shows the connection as "closing".

pid strace:

6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
6794  futex(0xa826de3c, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily u
navailable)
....

backtrace of spinning thread:

Thread 12 (Thread -1365873744 (LWP 14119)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7caa7db in __lll_mutex_lock_wait ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7ca7a03 in _L_mutex_lock_26 () from /lib/tls/i686/cmov/libpthread.so.0
#3  0x00000013 in ?? ()
#4  0x0000011f in ?? ()
#5  0xae9669b8 in ?? ()
#6  0x080e9468 in ?? ()
#7  0xb7d0e278 in ?? () from /usr/lib/libapr-0.so.0
#8  0xa8a5c2f8 in ?? ()
#9  0xae966998 in ?? ()
#10 0xb7d07a52 in apr_thread_mutex_lock () from /usr/lib/libapr-0.so.0
#11 0xb7d07a52 in apr_thread_mutex_lock () from /usr/lib/libapr-0.so.0
#12 0xb7d0ad1a in apr_allocator_set_mutex () from /usr/lib/libapr-0.so.0
#13 0xb7e4f545 in apr_bucket_free () from /usr/lib/libaprutil-0.so.0
#14 0xb7e4d999 in apr_bucket_shared_make () from /usr/lib/libaprutil-0.so.0
#15 0xb7e4e5a8 in apr_brigade_cleanup () from /usr/lib/libaprutil-0.so.0
#16 0xb7e4e55f in apr_bucket_pipe_create () from /usr/lib/libaprutil-0.so.0
#17 0xb7d0a42d in apr_pool_cleanup_run () from /usr/lib/libapr-0.so.0
#18 0xb7d09b6d in apr_pool_destroy () from /usr/lib/libapr-0.so.0
#19 0xb7d09b28 in apr_pool_clear () from /usr/lib/libapr-0.so.0
#20 0x08076e47 in ap_graceful_stop_signalled ()
#21 0xb7d04e56 in apr_threadattr_stacksize_set () from /usr/lib/libapr-0.so.0
#22 0xb7ca5ca3 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#23 0xb7c449ba in clone () from /lib/tls/i686/cmov/libc.so.6

I am not able to understand this backtrace, is it making any sense to anybody
else ? 

thanks
amund

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message