activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQCPP-199) Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
Date Tue, 18 Nov 2008 11:35:08 GMT


Timothy Bish commented on AMQCPP-199:

I think its safe to close this one as its related more to the segfault that we have fixed.

It looks to me like there's a deadlock in pyActiveMQ or in the test, thread two here is trying
to get a lock on something in python to deliver a message and thread one is trying to be closed
by what looks like a boost pointer going out of scope.  Note that the session executor attempting
to deliver a message is the one owned by the session that is being closed.

hread 2 (Thread 1100897168 (LWP 14973)):
#0  0x40000402 in __kernel_vsyscall ()
#1  0x0062725e in sem_wait@GLIBC_2.0 () from /lib/
#2  0x009a6f3b in PyThread_acquire_lock () from /usr/lib/
#3  0x0097e755 in PyEval_EvalFrame () from /usr/lib/
#4  0x00983c76 in PyEval_EvalCodeEx () from /usr/lib/
#5  0x00935cba in PyClassMethod_New () from /usr/lib/
#6  0x0091dd87 in PyObject_Call () from /usr/lib/
#7  0x00924388 in PyClass_IsSubclass () from /usr/lib/
#8  0x0091dd87 in PyObject_Call () from /usr/lib/
#9  0x0097d49c in PyEval_CallObjectWithKeywords () from /usr/lib/
#10 0x0099ebce in PyEval_CallFunction () from /usr/lib/
#11 0x4047d430 in boost::python::call<void, boost::python::handle<_object> > (callable=0x402cf2fc,
a0=@0x419e509c) at /usr/include/boost/python/call.hpp:63
#12 0x404ba2e7 in MessageListenerWrap::call_onMessage<cms::TextMessage> (this=0x953b660,
message=0x97a81d0) at src/main/MessageListener.cpp:76
#13 0x404ba7dd in MessageListenerWrap::onMessage (this=0x953b660, message=0x97a81d0) at src/main/MessageListener.cpp:58
#14 0x40734796 in activemq::core::ActiveMQConsumer::dispatch (this=0x9539878, data=@0x4214fd00)
at activemq/core/ActiveMQConsumer.cpp:489
#15 0x40759bb0 in activemq::core::ActiveMQSessionExecutor::dispatch (this=0x9466278, data=@0x4214fd00)
at activemq/core/ActiveMQSessionExecutor.cpp:185
#16 0x40759733 in activemq::core::ActiveMQSessionExecutor::dispatchAll (this=0x9466278) at
#17 0x40759809 in activemq::core::ActiveMQSessionExecutor::run (this=0x9466278) at activemq/core/ActiveMQSessionExecutor.cpp:208
#18 0x4082a69f in decaf::lang::Thread::runCallback (self=0x92ba998, param=0x96ea288) at decaf/lang/Thread.cpp:125
#19 0x40bb7e80 in dummy_worker (opaque=0x92ba998) at threadproc/unix/thread.c:142
#20 0x0062145b in start_thread () from /lib/
#21 0x00578c4e in clone () from /lib/

Thread 1 (Thread 1073832016 (LWP 10038)):
#0  0x40000402 in __kernel_vsyscall ()
#1  0x00627a3e in __lll_mutex_lock_wait () from /lib/
#2  0x006238b4 in _L_mutex_lock_760 () from /lib/
#3  0x00623758 in pthread_mutex_lock () from /lib/
#4  0x40ba7e44 in apr_thread_mutex_lock (mutex=0x96c9e20) at locks/unix/thread_mutex.c:92
#5  0x408433d1 in decaf::util::concurrent::Mutex::lock (this=0x94662b0) at decaf/util/concurrent/Mutex.cpp:52
#6  0x4070ecc5 in decaf::util::concurrent::Lock::lock (this=0xbf8f3514) at ./decaf/util/concurrent/Lock.h:94
#7  0x4070ee4e in Lock (this=0xbf8f3514, object=0x94662b0, intiallyLocked=true) at ./decaf/util/concurrent/Lock.h:66
#8  0x407594b4 in activemq::core::ActiveMQSessionExecutor::stop (this=0x9466278) at activemq/core/ActiveMQSessionExecutor.cpp:145
#9  0x40741779 in activemq::core::ActiveMQSession::stop (this=0x94661d8) at activemq/core/ActiveMQSession.cpp:827
#10 0x40745348 in activemq::core::ActiveMQSession::onConnectorResourceClosed (this=0x94661d8,
resource=0x9539820) at activemq/core/ActiveMQSession.cpp:663
#11 0x407d8bb1 in activemq::connector::BaseConnectorResource::close (this=0x9539820) at activemq/connector/BaseConnectorResource.cpp:66
#12 0x407360bb in activemq::core::ActiveMQConsumer::close (this=0x9539878) at activemq/core/ActiveMQConsumer.cpp:92
#13 0x40736618 in ~ActiveMQConsumer (this=0x9539878) at activemq/core/ActiveMQConsumer.cpp:68
#14 0x4049294b in ~auto_ptr (this=0x9306ebc) at /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c++/4.1.2/memory:259
#15 0x4049dfb3 in ~pointer_holder (this=0x9306eb4) at /usr/include/boost/python/object/pointer_holder.hpp:55
#16 0x40a8c57a in boost::python::objects::copy_class_object () from /usr/lib/

> Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
> ----------------------------------------------------------------
>                 Key: AMQCPP-199
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Decaf, Openwire
>    Affects Versions: 2.2.1
>         Environment: RHEL 5.2 (32 bits), apr-1.3.3, apr-util-1.3.4, ActiveMQ 5.1, gcc
4.1.2-42 (20071124), Java(TM) SE Runtime Environment (build 1.6.0_06-b02), pyactivemq-0.1.0rc1
>            Reporter: Alexander Martens
>            Assignee: Timothy Bish
>             Fix For: 2.2.2
>         Attachments: python.stress.log.gz, stress-again.tar.gz, stress-fc8.log.gz, stress-segfault-1.log.bz2,
stress-waits.tar.gz, stress.out
> We're getting occasional segmentation faults in our Python based application.
> The easiest way to reproduce it is by running pyactivemq's stress tests (src/tests/
> The offending line seems to be always the same.
> I send you attached a full gdb postmortem back-trace.
> Any help will be appreciated!

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

View raw message