activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-202) Occasional Deadlocks when Integration tests are run in a long loop on CentOS and REHL.
Date Mon, 10 Nov 2008 19:24:06 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47231#action_47231
] 

Timothy Bish commented on AMQCPP-202:
-------------------------------------

I just noticed something very peculiar in the back trace, there are two threads sitting at
a wait that look to be using the exact same object, which should never have created more than
one thread, very strange.  

{noformat}

Thread 3 (Thread 1094732688 (LWP 15620)):
#0  0x40000402 in __kernel_vsyscall ()
#1  0x005ac266 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0x4056c327 in apr_thread_cond_wait (cond=0x86813a0, mutex=0x40912ae8) at locks/unix/thread_cond.c:68
#3  0x4031e458 in decaf::util::concurrent::Mutex::wait (this=0x409030c0, millisecs=4294967295)
at decaf/util/concurrent/Mutex.cpp:116
#4  0x4031e13e in decaf::util::concurrent::Mutex::wait (this=0x409030c0) at decaf/util/concurrent/Mutex.cpp:82
#5  0x40238268 in activemq::core::ActiveMQSessionExecutor::run (this=0x409030a8) at activemq/core/ActiveMQSessionExecutor.cpp:222
#6  0x4030589f in decaf::lang::Thread::runCallback (self=0x858f488, param=0x40902f08) at decaf/lang/Thread.cpp:121
#7  0x4057aa1c in dummy_worker (opaque=0x858f488) at threadproc/unix/thread.c:142
#8  0x005a846b in start_thread () from /lib/libpthread.so.0
#9  0x004ffdbe in clone () from /lib/libc.so.6

Thread 2 (Thread 1098935184 (LWP 15621)):
#0  0x40000402 in __kernel_vsyscall ()
#1  0x005ac266 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0x4056c327 in apr_thread_cond_wait (cond=0x86813d8, mutex=0x40912ae8) at locks/unix/thread_cond.c:68
#3  0x4031e458 in decaf::util::concurrent::Mutex::wait (this=0x409030c0, millisecs=4294967295)
at decaf/util/concurrent/Mutex.cpp:116
#4  0x4031e13e in decaf::util::concurrent::Mutex::wait (this=0x409030c0) at decaf/util/concurrent/Mutex.cpp:82
#5  0x40238268 in activemq::core::ActiveMQSessionExecutor::run (this=0x409030a8) at activemq/core/ActiveMQSessionExecutor.cpp:222
#6  0x4030589f in decaf::lang::Thread::runCallback (self=0x858f488, param=0x40902f08) at decaf/lang/Thread.cpp:121
#7  0x4057aa1c in dummy_worker (opaque=0x858f488) at threadproc/unix/thread.c:142
#8  0x005a846b in start_thread () from /lib/libpthread.so.0
#9  0x004ffdbe in clone () from /lib/libc.so.6

{noformat}


> Occasional Deadlocks when Integration tests are run in a long loop on CentOS and REHL.
> --------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-202
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-202
>             Project: ActiveMQ C++ Client
>          Issue Type: Sub-task
>          Components: Integration Tests
>    Affects Versions: 2.2.1
>         Environment: CentOS and REHL so far.
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 2.2.2
>
>         Attachments: receiving.187.log.gz
>
>
> When run in a continuous loop the integration tests have been seen to deadlock.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message