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 "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org> on 2005/01/19 12:03:16 UTC
[jira] Created: (AXISCPP-390) Memory leaks in case of SOAPFault
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
[jira] Commented: (AXISCPP-390) Memory leaks in case of SOAPFault
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-390?page=comments#action_57769 ]
Samisa Abeysinghe commented on AXISCPP-390:
-------------------------------------------
Here is a sample code segment of the generated code. Note that pSoapFault is passed to the Calculator_AxisClientException constructor. And Calculator_AxisClientException class does not clean up this pointer.
catch(AxisException& e)
{
int iExceptionCode = e.getExceptionCode();
if(AXISC_NODE_VALUE_MISMATCH_EXCEPTION != iExceptionCode)
{
throw Calculator_AxisClientException(e.what());
}
=> ISoapFault* pSoapFault = (ISoapFault*) m_pCall->checkFault("Fault","http://localhost/axis/Calculator" );
if(pSoapFault)
{
m_pCall->unInitialize();
throw Calculator_AxisClientException(pSoapFault);
}
else throw;
}
> 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
[jira] Commented: (AXISCPP-390) Memory leaks in case of SOAPFault
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Closed: (AXISCPP-390) Memory leaks in case of SOAPFault
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-390?page=history ]
Samisa Abeysinghe closed AXISCPP-390:
-------------------------------------
Resolution: Invalid
This issue is invaalis because the SOAP fault exception model was changed with updates to the Exception class hierarcy. These updates were done by Mark.
> 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