Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <1607661213.1144242330754.JavaMail.jira@ajax>
Date: Wed, 5 Apr 2006 14:05:30 +0100 (BST)
From: "Fred Preston (JIRA)" <axis-c-dev@ws.apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Closed: (AXISCPP-209) Client crashes when soap method
 invoked repeatedly in a loop
In-Reply-To: <843364755.1098184491036.JavaMail.apache@nagoya>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/AXISCPP-209?page=all ]
     
Fred Preston closed AXISCPP-209:
--------------------------------


> Client crashes when soap method invoked repeatedly in a loop
> ------------------------------------------------------------
>
>          Key: AXISCPP-209
>          URL: http://issues.apache.org/jira/browse/AXISCPP-209
>      Project: Axis-C++
>         Type: Bug

>   Components: Basic Architecture
>     Versions: 1.3 Beta
>  Environment: windows 2000 / sp 4
>     Reporter: sanjaya singharage
>     Assignee: Samisa Abeysinghe
>      Fix For: 1.5 Final
>  Attachments: InteropBaseClient.cpp
>
> This bug can be reproduced with the largestring test in tests/performance/large_string. for 1 and 2 iterations the test succeeds. If more iterations are specified the test fails. The relvant loop is listed below.
>         for(int i=1;i<=charlength;i++)
>         { 
>             sendbuf = (char*)malloc(sizeof(char)*(i+1));
>             memset(sendbuf, 's', i);
>             *(sendbuf+i) = '\0';
>             echoStringResult = ws.echoString(sendbuf);
>             if (0 == strcmp(echoStringResult, sendbuf))            
>             {
>                 printf("%d%s", i, "length string Successful\n");
>             }
>             else
>             {
>                 printf("%d%s", i, "length string FAILED\n");
>             }
>             printf("%s\n",echoStringResult );
>             free (sendbuf);
>             sendbuf = NULL;
>             if(echoStringResult)
>                 free(echoStringResult);
>          } 
> The crashing behaviour is summarised as follows.
> Client built in Release mode
> ---------------------------
> Expat parser - crashed on the third iteration on freeing echoStringResult 
> (
> i.e             if(echoStringResult)
>                 free(echoStringResult);
> )
> Xerces parser - crashed on the third interation on invoking 
> echoString method
> (i.e.
> echoStringResult = ws.echoString(sendbuf);
> )
> Client built in Debug mode
> --------------------------
> For both Expat and Xerces the client crashes on the first iteration 
> on freein echoStringResult
> (
> i.e             if(echoStringResult)
>                 free(echoStringResult);
> )
> This means that debugging the problem is not possible. The problem needs to be traced by printf s. Apparently this problems does not exist in Linux. Any ideas?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira