axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-390) Memory leaks in case of SOAPFault
Date Wed, 19 Jan 2005 11:14:17 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-390?page=comments#action_57768 ]
     
Samisa Abeysinghe commented on AXISCPP-390:
-------------------------------------------

Resolving this issue is a bit complex given that we pass the pointer to the SOAP fault object
to the client exception constructor. Either we have to make the exception constructor do a
deep copy of the fault object and delete the fault object before we throw the exception. Or
alternatively we could pass the required values to the exception and delete the fault object
before we throw the exception object.
It is not a good idea to delete the SOAP fault from within the Exception destructor as of
now, because we have a shallow copy of the SOAP fault inside the exception class.

> Memory leaks in case of SOAPFault
> ---------------------------------
>
>          Key: AXISCPP-390
>          URL: http://issues.apache.org/jira/browse/AXISCPP-390
>      Project: Axis-C++
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.4 Final
>  Environment: All platforms
>     Reporter: Samisa Abeysinghe
>      Fix For: 1.5 Alpha

>
> The pointer returned to the SOAPFault object is never deallocated in the generated code
in case of a fault. The pointer is returned by Call::checkFault() method and memory is allocated
by SoapDeSerializer::checkForFault()

-- 
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


Mime
View raw message