[
http://issues.apache.org/jira/browse/AXISCPP-707?page=comments#action_12314753
]
Dushshantha Chandradasa commented on AXISCPP-707:
-------------------------------------------------
I made a fix on this and tested the following scenarios.
1. Exchanged the HTTPTransport.dll and HTTPChannel.dll file names
2. Tested with a an older version of dll file i used AxisTransport.dll
instead of HTTPTransport.dll
3. Tested with wrong endpoints of clients
4. Missing dll files
I got correct exception messages for the above test scenarios and server is
working without any crash.
Any ideas for more scenerios to be tested??
> Incorrect use of delete in AxisEngineException::processException()
> ------------------------------------------------------------------
>
> Key: AXISCPP-707
> URL: http://issues.apache.org/jira/browse/AXISCPP-707
> Project: Axis-C++
> Type: Bug
> Components: Server - Engine
> Versions: current (nightly)
> Environment: Windows XP Pro, VS2003
> Reporter: Henrik Nordberg
> Assignee: Dushshantha Chandradasa
> Priority: Critical
>
> There is a delete statement in AxisEngineException::processException() which
> has a couple of problems:
> First, if you were supposed to delete the pointer passed in, delete[] should
> be used (in C++). But, at least in the case of the exception thrown when a
> library fails to load, a constant character pointer is passed in (in this
> case "") -- see this line in XMLParserFactory::loadLib():
> throw AxisEngineException(SERVER_ENGINE_LOADING_PARSER_FAILED,
> PLATFORM_LOADLIB_ERROR);
> Why not just use a const std::string& instead of char*?
--
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
