qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From trivedi_ravi13 <trivedi_rav...@yahoo.co.in>
Subject Qpid clients getting crashed probably while sending heartbeats
Date Fri, 02 May 2014 17:05:23 GMT
I have almost 15-20 clients running on my system. all clients use heartbeat
to detect connection failure. these clients started to get crashed randomly
after enabling heartbeat. Timeout is set to 2 sec for some app and 5 sec for
others. Below is attached core dump output. It appears to be getting
terminated in qpid::sys:Timer::run() method.


(gdb) bt full
#0  0x0fe76444 in raise () from /lib/libc.so.6
No symbol table info available.
#1  0x0fe7b694 in abort () from /lib/libc.so.6
No symbol table info available.
#2  0x0fe6d778 in __assert_fail () from /lib/libc.so.6
No symbol table info available.
#3  0x0f9357d8 in qpid::sys::Timer::run() () from
/usr/lib/libqpidcommon.so.2
No symbol table info available.
#4  0x0f803984 in ?? () from /usr/lib/libqpidcommon.so.2
No symbol table info available.
#5  0x0fd76d8c in ?? () from /lib/libpthread.so.0
No symbol table info available.
#6  0x0ff25a90 in clone () from /lib/libc.so.6
No symbol table info available.


We need this feature to detect failure as soon as possible. Is there any
other way to do that. I believe SO_KEEPALIVE is not set in sockets in qpid. 



--
View this message in context: http://apache-qpid-developers.2158895.n2.nabble.com/Qpid-clients-getting-crashed-probably-while-sending-heartbeats-tp7594410.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message