From axis-c-dev-return-20978-apmail-ws-axis-c-dev-archive=ws.apache.org@ws.apache.org Mon Jun 22 09:40:21 2009 Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 83048 invoked from network); 22 Jun 2009 09:40:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Jun 2009 09:40:21 -0000 Received: (qmail 685 invoked by uid 500); 22 Jun 2009 09:40:32 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 653 invoked by uid 500); 22 Jun 2009 09:40:31 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 644 invoked by uid 99); 22 Jun 2009 09:40:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 09:40:31 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 09:40:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7A415234C004 for ; Mon, 22 Jun 2009 02:40:07 -0700 (PDT) Message-ID: <2074415370.1245663607493.JavaMail.jira@brutus> Date: Mon, 22 Jun 2009 02:40:07 -0700 (PDT) From: "Damitha Kumarage (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Created: (AXIS2C-1378) operation name is corruputed by the time it reaches dispatcher MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org operation name is corruputed by the time it reaches dispatcher -------------------------------------------------------------- Key: AXIS2C-1378 URL: https://issues.apache.org/jira/browse/AXIS2C-1378 Project: Axis2-C Issue Type: Bug Components: core/engine Reporter: Damitha Kumarage I have following valgrind info when running Axis2/C with Apache module. ==8599== Invalid read of size 1 ==8599== at 0x40276E8: strlen (mc_replace_strmem.c:242) ==8599== by 0x41866D7: vfprintf (in /lib/tls/i686/cmov/libc-2.9.so) ==8599== by 0x423E771: __vsnprintf_chk (in /lib/tls/i686/cmov/libc-2.9.so) ==8599== by 0x47A824E: axutil_log_impl_log_debug (stdio2.h:78) ==8599== by 0x46DE5DA: axis2_addr_disp_find_op (addr_disp.c:192) ==8599== by 0x46FFD6A: axis2_msg_ctx_find_op (msg_ctx.c:2094) ==8599== by 0x46DF6BA: axis2_disp_find_svc_and_op (disp.c:165) ==8599== by 0x46DE330: axis2_addr_disp_invoke (addr_disp.c:269) ==8599== by 0x46D784C: axis2_handler_invoke (handler.c:91) ==8599== by 0x46DD783: axis2_phase_invoke (phase.c:230) ==8599== by 0x46E0FFD: axis2_engine_invoke_phases (engine.c:691) ==8599== by 0x46E1A98: axis2_engine_receive (engine.c:249) ==8599== Address 0x4412ae0 is 6,800 bytes inside a block of size 8,192 free'd ==8599== at 0x4025DFA: free (vg_replace_malloc.c:323) ==8599== by 0x40D7289: apr_allocator_destroy (apr_pools.c:134) ==8599== by 0x46AEB35: axis2_handler (mod_axis2.c:381) ==8599== by 0x8081520: ap_run_handler (config.c:157) ==8599== by 0x8081C70: ap_invoke_handler (config.c:372) ==8599== by 0x80B78D3: ap_process_request (http_request.c:258) ==8599== by 0x80B46EC: ap_process_http_connection (http_core.c:190) ==8599== by 0x808A192: ap_run_process_connection (connection.c:43) ==8599== by 0x808A612: ap_process_connection (connection.c:178) ==8599== by 0x80F4C36: child_main (prefork.c:650) ==8599== by 0x80F4D29: make_child (prefork.c:690) ==8599== by 0x80F52CD: ap_mpm_run (prefork.c:966) You can reproduce this by running echo sample with the following code added to addr_disp.c if(op) { axutil_qname_t *qname = (axutil_qname_t *) axis2_op_get_qname(op, env); AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "opname:%s", axutil_qname_to_string(qname, env)); } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.