axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ellen Chou <ellen.c...@gmail.com>
Subject axis2_http_server crash after stress test
Date Tue, 19 Jul 2011 05:37:39 GMT
Hi all,

We launched 5 processes of SOAP clients.  Each client process sends request
continuously at 1 second interval to our SOAP server developed with axis2c
1.5.0.  axis2_http_server process crashes after 2 hours.   Free memory kept
going down, yet the process memory seems stable.  There are 2 cases of back
trace dump:

*** glibc detected *** ./axis2_http_server: malloc(): memory corruption:
0x5a50b1b0 ***
======= Backtrace: =========
/lib/libc.so.6[0x2de583]
/lib/libc.so.6(__libc_malloc+0x7e)[0x2dfebe]
/axis2c/lib/libaxutil.so.0(axutil_allocator_malloc_impl+0x1d)[0x176b1d]
/axis2c/lib/libaxis2_http_common.so.0(axis2_http_header_create+0x2c)[0x134b6c]
/axis2c/lib/libaxis2_http_common.so.0(axis2_http_worker_process_request+0x21e)[0x1393de]
/axis2c/lib/libaxis2_http_receiver.so.0(axis2_svr_thread_worker_func+0xb1)[0x217ea1]
/axis2c/lib/libaxutil.so.0[0x1887b6]
/lib/libpthread.so.0[0x24b44b]
/lib/libc.so.6(clone+0x5e)[0x34680e]
======= Memory map: ========
00110000-0012b000 r-xp 00000000 08:02 165014     /lib/ld-2.6.so
0012b000-0012c000 r-xp 0001a000 08:02 165014     /lib/ld-2.6.so
0012c000-0012d000 rwxp 0001b000 08:02 165014     /lib/ld-2.6.so
....

*** glibc detected *** ./axis2_http_server: free(): invalid next size
(fast): 0x088fbcd0 ***
======= Backtrace: =========
/lib/libc.so.6[0x2dddf1]
/lib/libc.so.6(cfree+0x90)[0x2e1430]
/axis2c/lib/libaxutil.so.0(axutil_allocator_free_impl+0x1d)[0x176abd]
/axis2c/lib/libaxis2_http_common.so.0(axis2_http_worker_process_request+0x22f)[0x1393ef]
/axis2c/lib/libaxis2_http_receiver.so.0(axis2_svr_thread_worker_func+0xb1)[0x217ea1]
/axis2c/lib/libaxutil.so.0[0x1887b6]
/lib/libpthread.so.0[0x24b44b]
/lib/libc.so.6(clone+0x5e)[0x34680e]
======= Memory map: ========
00110000-0012b000 r-xp 00000000 08:02 197590     /lib/ld-2.6.so
....

Have any one of you seen this problem?  Is the problem fixed in Axis2C 1.6
or 1.7?

Thanks,
Ellen

Mime
View raw message