[
https://issues.apache.org/activemq/browse/AMQCPP-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50578#action_50578
]
Dario Laverde commented on AMQCPP-205:
--------------------------------------
hi all,
any progress on this issue? I have a similar deadlock as follows:
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xf785e266 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0xf787f19a in apr_thread_cond_wait (cond=0xadf4b48, mutex=0xadf4b18) at
locks/unix/thread_cond.c:68
#3 0xf7b130b2 in decaf::util::concurrent::Mutex::wait (this=0xa896f74,
millisecs=4294967295) at decaf/util/concurrent/Mutex.cpp:116
#4 0xf7b12fa5 in decaf::util::concurrent::Mutex::wait (this=0xa896f74) at
decaf/util/concurrent/Mutex.cpp:82
#5 0xf7b145f6 in decaf::util::concurrent::CountDownLatch::await
(this=0xa896f6c) at decaf/util/concurrent/CountDownLatch.cpp:53
#6 0xf7aaf0c5 in activemq::transport::filters::FutureResponse::getResponse
(this=0xa896f68) at ./activemq/transport/filters/FutureResponse.h:60
#7 0xf7aacce2 in activemq::transport::filters::ResponseCorrelator::request
(this=0xa195eb0, command=0xa249918) at
activemq/transport/filters/ResponseCorrelator.cpp:93
#8 0xf7a7ba83 in
activemq::connector::openwire::OpenWireFormatNegotiator::request
(this=0xa1969c8, command=0xa249918) at
activemq/connector/openwire/OpenWireFormatNegotiator.cpp:104
#9 0xf7a834f9 in activemq::connector::openwire::OpenWireConnector::syncRequest
(this=0xa195f88, command=0xa249918, timeout=0) at
activemq/connector/openwire/OpenWireConnector.cpp:1512
#10 0xf7a86599 in
activemq::connector::openwire::OpenWireConnector::createProducer
(this=0xa195f88, destination=0xa873de0, session=0xa0c48c8)
at activemq/connector/openwire/OpenWireConnector.cpp:641
#11 0xf7a16b78 in activemq::core::ActiveMQSession::createProducer
(this=0xa0b7b48, destination=0xa873de0) at activemq/core/ActiveMQSession.cpp:346
which seems to have been triggered by:
2009-03-16 14:20:12,840 [rt: vm://null#2] WARN DemandForwardingBridge
- Caught an exception processing local command
org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://null#3)
disposed.
at
org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:87)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:652)
at
org.apache.activemq.network.DemandForwardingBridgeSupport$1.onCommand(DemandForwardingBridgeSupport.java:147)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:104)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at
org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:205)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
this is with latest stable releases - any pointers appreciated (i.e. if this
relates to other bugs or if I should open a new bug)
> CmsTemplate testBasics test can hang
> ------------------------------------
>
> Key: AMQCPP-205
> URL: https://issues.apache.org/activemq/browse/AMQCPP-205
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Integration Tests
> Affects Versions: 2.2.1, 2.2.2
> Environment: CentOS / REHL
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 3.0
>
> Attachments: cmstemplate.segfault-1.log.gz, receiving.187.log.gz
>
>
> Running the CmsTemplate integration tests in a loop can result in a hang.
> The code appears to be deadlocked when two threads that share the same
> instance of an ActiveMQSessionExecutor are run.
> This snippet from a backtrace shows the case:
> {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}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
