activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: process abort
Date Tue, 29 Nov 2011 11:16:15 GMT
On Tue, 2011-11-29 at 17:20 +0900, Nishizawa Kenji wrote:
> Hi.
> 
> our app suddenly aborted and core file was generated.
> the result of examining the core by gdb is as follows.
> 
> #0  0x000000385fc30215 in raise () from /lib64/libc.so.6
> #1  0x000000385fc31cc0 in abort () from /lib64/libc.so.6
> #2  0x0000003871abec44 in __gnu_cxx::__verbose_terminate_handler ()
>    from /usr/lib64/libstdc++.so.6
> #3  0x0000003871abcdb6 in ?? () from /usr/lib64/libstdc++.so.6
> #4  0x0000003871abcde3 in std::terminate () from
> /usr/lib64/libstdc++.so.6
> #5  0x0000003871abcdf6 in ?? () from /usr/lib64/libstdc++.so.6
> #6  0x0000003871abc848 in __cxa_call_unexpected () from
> /usr/lib64/libstdc++.so.6
> #7  0x000000000045e0b6 in sbcvsvc::onMessage (this=3D0x7fff12f8c7d0,
> msg=3D@0x53fa15e0,
>     sendsubject=3D@0x53fa1570) at sbcvsvc.cpp:361
> #8  0x000000000046b19f in AisAppSimple::onMessage =
> (this=3D0x7fff12f8c7d0,
>     replier=3D@0x53fa1c70, message=3D@0x53fa15e0) at
> application/AisAppSimple.cpp:681
> #9  0x0000000000493a82 in AisMessageCallback::onMessage =
> (this=3D0x8dc21c0,
>     msg=3D0x2aaaac0020c0) at event/AisMessageCallback.cpp:99
> #10 0x00002afc97e4cebc in activemq::core::ActiveMQConsumer::dispatch
> (this=3D0x8dc35e0,
>     dispatch=3D@0x53fa1ec0) at activemq/core/ActiveMQConsumer.cpp:971
> #11 0x00002afc97e6c66a in
> activemq::core::ActiveMQSessionExecutor::dispatch (
>     this=3D0x8dc3320, dispatch=3D@0x53fa1ec0)
>     at activemq/core/ActiveMQSessionExecutor.cpp:128
> #12 0x00002afc97e6c0fe in
> activemq::core::ActiveMQSessionExecutor::iterate ( preview wiki markup
> help Patch Info Patch Available=20
> 
>     this=3D0x8dc3320) at activemq/core/ActiveMQSessionExecutor.cpp:166
> #13 0x00002afc97ea5df2 in activemq::threads::DedicatedTaskRunner::run
> (this=3D0x8dc2c30)
>     at activemq/threads/DedicatedTaskRunner.cpp:111
> #14 0x00002afc980b5ac8 in decaf::lang::ThreadProperties::runCallback (
>     properties=3D0x8dc2130) at decaf/lang/Thread.cpp:135
> #15 0x00002afc980b329b in threadWorker (arg=3D0x8dc2130) at
> decaf/lang/Thread.cpp:188
> #16 0x0000003860806367 in start_thread () from /lib64/libpthread.so.0
> #17 0x000000385fcd30ad in clone () from /lib64/libc.so.6
> 
> first question: is this problem caused by following
> https://issues.apache.org/jira/si/jira.issueviews:issue-html/AMQCPP-354/
> AMQCPP-354.html
> 
> otherwise, i hope to get the cause and way to avoid this.
> 
> our environment is belows
> 
> client: CMS(C++client) 3.1.3
> Activemq: 5.3.1
> Linux version 2.6.18-128.el5 (mockbuild@hs20-bc1-7.build.redhat.com)
> (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Dec 17
> 11:41:38 EST 2008
> SMP: Allowing 8 CPUs, 4 hotplug CPUs
> Memory: 20416636k/21757948k available (2494k kernel code, 552784k
> reserved, 1263k data, 200k init)
> 
> thanks and regards,
> Kenji
> 
> 

The error appears to have occurred in your onMessage callback, might
want to examine your code to see what could be causing the segfault
there.  Otherwise the best thing to do is update to the latest release
of ActiveMQ-CPP v3.4.0

Regards


-- 
Tim Bish
------------
FuseSource
Email: tim.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/




Mime
View raw message