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 ax...@ws.apache.org on 2004/10/19 13:14:51 UTC
[jira] Created: (AXISCPP-209) Client crashes when soap method invoked repeatedly in a loop
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-209
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-209
Summary: Client crashes when soap method invoked repeatedly in a loop
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Basic Architecture
Versions:
1.3 Beta
Assignee:
Reporter: sanjaya singharage
Created: Tue, 19 Oct 2004 4:14 AM
Updated: Tue, 19 Oct 2004 4:14 AM
Environment: windows 2000 / sp 4
Description:
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?
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-209) Client crashes when soap method
invoked repeatedly in a loop
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Resolved: (AXISCPP-209) Client crashes when soap method invoked repeatedly in a loop
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-209?page=history ]
Samisa Abeysinghe resolved AXISCPP-209:
---------------------------------------
Resolution: Fixed
Fix Version: 1.5 Final
The tests did not revealed any problems.
May be the problems are fixed automatically with other fixes done.
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXISCPP-209) Client crashes when soap method invoked repeatedly in a loop
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-209?page=history ]
Fred Preston reassigned AXISCPP-209:
------------------------------------
Assign To: (was: Fred Preston)
> Client crashes when soap method invoked repeatedly in a loop
> ------------------------------------------------------------
>
> Key: AXISCPP-209
> URL: http://nagoya.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
>
> 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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-209) Client crashes when soap method invoked repeatedly in a loop
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-209?page=history ]
Samisa Abeysinghe updated AXISCPP-209:
--------------------------------------
Attachment: InteropBaseClient.cpp
I tested with this client and the base.wsdl and there are no problems
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXISCPP-209) Client crashes when soap method invoked repeatedly in a loop
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-209?page=history ]
John Hawkins reassigned AXISCPP-209:
------------------------------------
Assign To: Fred Preston
> 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: Fred Preston
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXISCPP-209) Client crashes when soap method invoked repeatedly in a loop
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-209?page=history ]
Samisa Abeysinghe reassigned AXISCPP-209:
-----------------------------------------
Assign To: Samisa Abeysinghe
> 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
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira