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/02/09 11:18:11 UTC
[jira] Closed: (AXISCPP-413) HandlerPool class has potential memory leak
[ http://issues.apache.org/jira/browse/AXISCPP-413?page=history ]
Samisa Abeysinghe closed AXISCPP-413:
-------------------------------------
Resolution: Fixed
It is very unlikely to cause any memory leak here.
I did apply the memory management BP anyway.
> HandlerPool class has potential memory leak
> -------------------------------------------
>
> Key: AXISCPP-413
> URL: http://issues.apache.org/jira/browse/AXISCPP-413
> Project: Axis-C++
> Type: Improvement
> Components: Basic Architecture
> Versions: 1.5 Final
> Reporter: Chinthana Danapala
> Priority: Minor
>
> In HandlerPool.cpp in below method have missed some best practices
> int HandlerPool::getHandlerChain (string &sSessionId, HandlerChain** ppChain,
> const WSDDHandlerList* pHandlerList)
> {
>
> HandlerChain* pChain; *declared but not been initialized in same time
> WSDDHandler* pWSDDH;
> BasicHandler* pBH;
> }
--
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