You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Frederic Heem (JIRA)" <ji...@apache.org> on 2008/06/30 18:59:45 UTC

[jira] Created: (AXIS2C-1214) memory leak when server returns an error

memory leak when server returns an error
----------------------------------------

                 Key: AXIS2C-1214
                 URL: https://issues.apache.org/jira/browse/AXIS2C-1214
             Project: Axis2-C
          Issue Type: Bug
    Affects Versions: Current (Nightly)
         Environment: linux fc6
            Reporter: Frederic Heem


In-Only message has been invoked 3 times on the client side, the server reponds with an error (see bug AXIS2C-1213), memory is leaked as shown by valgrind.

==21539== 54 bytes in 3 blocks are definitely lost in loss record 49 of 57
==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
==21539==    by 0x40512C8: axutil_strdup (string.c:282)
==21539==    by 0x402B912: axiom_node_to_string (om_node.c:1213)
==21539==    by 0x409D2F7: axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync (raw_xml_in_out_msg_recv.c:384)
==21539==    by 0x409C303: axis2_msg_recv_invoke_business_logic (msg_recv.c:397)
==21539==    by 0x409C933: axis2_msg_recv_receive_impl (msg_recv.c:319)
==21539==    by 0x409C383: axis2_msg_recv_receive (msg_recv.c:436)
==21539==    by 0x4091B43: axis2_engine_receive (engine.c:318)
==21539==    by 0x4019DAD: axis2_http_transport_utils_process_http_post_request (http_transport_utils.c:658)
==21539==    by 0x4016B03: axis2_http_worker_process_request (http_worker.c:908)
==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
==21539==
==21539==
==21539== 264 (48 direct, 216 indirect) bytes in 3 blocks are definitely lost in loss record 51 of 57
==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
==21539==    by 0x40129DF: axis2_http_status_line_create (http_status_line.c:46)
==21539==    by 0x40176AC: axis2_http_worker_process_request (http_worker.c:1244)
==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)
==21539==
==21539==
==21539== 1,809 (792 direct, 1,017 indirect) bytes in 3 blocks are definitely lost in loss record 56 of 57
==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
==21539==    by 0x8074862: axis2_msg_ctx_create (msg_ctx.c:230)
==21539==    by 0x4090F04: axis2_engine_create_fault_msg_ctx (engine.c:533)
==21539==    by 0x4016BEA: axis2_http_worker_process_request (http_worker.c:1216)
==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)


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


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


[jira] Commented: (AXIS2C-1214) memory leak when server returns an error

Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2C-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609541#action_12609541 ] 

Supun Kamburugamuva commented on AXIS2C-1214:
---------------------------------------------

Hi Frederic,

Does this issue still exists? I have checked with the notify sample with MEP specified and unspecified. But no memory leaks. 

Supun.. 

> memory leak when server returns an error
> ----------------------------------------
>
>                 Key: AXIS2C-1214
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1214
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: Current (Nightly)
>         Environment: linux fc6
>            Reporter: Frederic Heem
>
> In-Only message has been invoked 3 times on the client side, the server reponds with an error (see bug AXIS2C-1213), memory is leaked as shown by valgrind.
> ==21539== 54 bytes in 3 blocks are definitely lost in loss record 49 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x40512C8: axutil_strdup (string.c:282)
> ==21539==    by 0x402B912: axiom_node_to_string (om_node.c:1213)
> ==21539==    by 0x409D2F7: axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync (raw_xml_in_out_msg_recv.c:384)
> ==21539==    by 0x409C303: axis2_msg_recv_invoke_business_logic (msg_recv.c:397)
> ==21539==    by 0x409C933: axis2_msg_recv_receive_impl (msg_recv.c:319)
> ==21539==    by 0x409C383: axis2_msg_recv_receive (msg_recv.c:436)
> ==21539==    by 0x4091B43: axis2_engine_receive (engine.c:318)
> ==21539==    by 0x4019DAD: axis2_http_transport_utils_process_http_post_request (http_transport_utils.c:658)
> ==21539==    by 0x4016B03: axis2_http_worker_process_request (http_worker.c:908)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==
> ==21539==
> ==21539== 264 (48 direct, 216 indirect) bytes in 3 blocks are definitely lost in loss record 51 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x40129DF: axis2_http_status_line_create (http_status_line.c:46)
> ==21539==    by 0x40176AC: axis2_http_worker_process_request (http_worker.c:1244)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
> ==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)
> ==21539==
> ==21539==
> ==21539== 1,809 (792 direct, 1,017 indirect) bytes in 3 blocks are definitely lost in loss record 56 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x8074862: axis2_msg_ctx_create (msg_ctx.c:230)
> ==21539==    by 0x4090F04: axis2_engine_create_fault_msg_ctx (engine.c:533)
> ==21539==    by 0x4016BEA: axis2_http_worker_process_request (http_worker.c:1216)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
> ==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)

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


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


[jira] Commented: (AXIS2C-1214) memory leak when server returns an error

Posted by "Frederic Heem (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2C-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609554#action_12609554 ] 

Frederic Heem commented on AXIS2C-1214:
---------------------------------------

Indeed, the memory leaks still exists. However, It occurs only when the server returns an error. It's true that since the server no longer returns an error, no memory is seen. Let's say that the leak is "hidden" but present. 
Regards,

> memory leak when server returns an error
> ----------------------------------------
>
>                 Key: AXIS2C-1214
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1214
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: Current (Nightly)
>         Environment: linux fc6
>            Reporter: Frederic Heem
>
> In-Only message has been invoked 3 times on the client side, the server reponds with an error (see bug AXIS2C-1213), memory is leaked as shown by valgrind.
> ==21539== 54 bytes in 3 blocks are definitely lost in loss record 49 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x40512C8: axutil_strdup (string.c:282)
> ==21539==    by 0x402B912: axiom_node_to_string (om_node.c:1213)
> ==21539==    by 0x409D2F7: axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync (raw_xml_in_out_msg_recv.c:384)
> ==21539==    by 0x409C303: axis2_msg_recv_invoke_business_logic (msg_recv.c:397)
> ==21539==    by 0x409C933: axis2_msg_recv_receive_impl (msg_recv.c:319)
> ==21539==    by 0x409C383: axis2_msg_recv_receive (msg_recv.c:436)
> ==21539==    by 0x4091B43: axis2_engine_receive (engine.c:318)
> ==21539==    by 0x4019DAD: axis2_http_transport_utils_process_http_post_request (http_transport_utils.c:658)
> ==21539==    by 0x4016B03: axis2_http_worker_process_request (http_worker.c:908)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==
> ==21539==
> ==21539== 264 (48 direct, 216 indirect) bytes in 3 blocks are definitely lost in loss record 51 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x40129DF: axis2_http_status_line_create (http_status_line.c:46)
> ==21539==    by 0x40176AC: axis2_http_worker_process_request (http_worker.c:1244)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
> ==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)
> ==21539==
> ==21539==
> ==21539== 1,809 (792 direct, 1,017 indirect) bytes in 3 blocks are definitely lost in loss record 56 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x8074862: axis2_msg_ctx_create (msg_ctx.c:230)
> ==21539==    by 0x4090F04: axis2_engine_create_fault_msg_ctx (engine.c:533)
> ==21539==    by 0x4016BEA: axis2_http_worker_process_request (http_worker.c:1216)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
> ==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)

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


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


[jira] Updated: (AXIS2C-1214) memory leak when server returns an error

Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S.Uthaiyashankar updated AXIS2C-1214:
-------------------------------------

      Component/s: core/engine
    Fix Version/s: 1.6.0
         Assignee: S.Uthaiyashankar

> memory leak when server returns an error
> ----------------------------------------
>
>                 Key: AXIS2C-1214
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1214
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/engine
>    Affects Versions: Current (Nightly)
>         Environment: linux fc6
>            Reporter: Frederic Heem
>            Assignee: S.Uthaiyashankar
>             Fix For: 1.6.0
>
>
> In-Only message has been invoked 3 times on the client side, the server reponds with an error (see bug AXIS2C-1213), memory is leaked as shown by valgrind.
> ==21539== 54 bytes in 3 blocks are definitely lost in loss record 49 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x40512C8: axutil_strdup (string.c:282)
> ==21539==    by 0x402B912: axiom_node_to_string (om_node.c:1213)
> ==21539==    by 0x409D2F7: axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync (raw_xml_in_out_msg_recv.c:384)
> ==21539==    by 0x409C303: axis2_msg_recv_invoke_business_logic (msg_recv.c:397)
> ==21539==    by 0x409C933: axis2_msg_recv_receive_impl (msg_recv.c:319)
> ==21539==    by 0x409C383: axis2_msg_recv_receive (msg_recv.c:436)
> ==21539==    by 0x4091B43: axis2_engine_receive (engine.c:318)
> ==21539==    by 0x4019DAD: axis2_http_transport_utils_process_http_post_request (http_transport_utils.c:658)
> ==21539==    by 0x4016B03: axis2_http_worker_process_request (http_worker.c:908)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==
> ==21539==
> ==21539== 264 (48 direct, 216 indirect) bytes in 3 blocks are definitely lost in loss record 51 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x40129DF: axis2_http_status_line_create (http_status_line.c:46)
> ==21539==    by 0x40176AC: axis2_http_worker_process_request (http_worker.c:1244)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
> ==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)
> ==21539==
> ==21539==
> ==21539== 1,809 (792 direct, 1,017 indirect) bytes in 3 blocks are definitely lost in loss record 56 of 57
> ==21539==    at 0x4005858: malloc (vg_replace_malloc.c:207)
> ==21539==    by 0x8074862: axis2_msg_ctx_create (msg_ctx.c:230)
> ==21539==    by 0x4090F04: axis2_engine_create_fault_msg_ctx (engine.c:533)
> ==21539==    by 0x4016BEA: axis2_http_worker_process_request (http_worker.c:1216)
> ==21539==    by 0x4123ED0: axis2_svr_thread_worker_func (http_svr_thread.c:259)
> ==21539==    by 0x405EF55: dummy_worker (thread_unix.c:93)
> ==21539==    by 0x8E145A: start_thread (in /lib/libpthread-2.5.so)
> ==21539==    by 0x71323D: clone (in /lib/libc-2.5.so)

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