Hi Adrian,
Thank you, I have read the page and followed the instructions. My C++ knowledge
is more than 8 years old, so I'm not sure I catched every single instruction.
My code is very simple:
xsd__string EosServiceWS::search(xsd__int Value0){
xsd__string retBuf = new char[100];
sprintf_s(retBuf, 100, Search: %i, Value0);
return retBuf;
}
xsd__string EosServiceWS::suche(xsd__string Value0) {
int size = strlen(Value0) + 10;
xsd__string retBuf = new char[size];
sprintf_s((char*) retBuf, size, Suche: %s, Value0);
delete Value0;
return retBuf;
}
void EosServiceWS::test(){
cout WS-Call to test() endl;
}
I found the memory leak while calling method test().
Btw, I'm using Visual Studio 2005 and will switch to Visual Studio 2003.
In the mailing list I read in some postings that Xerces may cause the memory
leak. Is that confirmed? Can I use the current version instead of xerces 2.2?
Thnaks,
Markus
-Ursprüngliche Nachricht-
Von: Adrian Dick [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 11. Oktober 2006 12:38
An: Apache AXIS C User List
Betreff: Re: Memory Leak with version1.6b
Hi,
Have you followed the advice given here:
http://ws.apache.org/axis/cpp/arch/mem-management.html
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
Markus Heinisch [EMAIL PROTECTED] wrote on 11/10/2006
10:15:48:
Hello,
I'm new to AXIS_CPP. I have managed to deploy my own sample Web
service with the simple axis server on Win XP (using Visual
Studio 2005).
While testing my Web service with SoapUi, I discovered a
memory leak!
My Web service is very simple and based on the class:
class EosServiceWS
{
public:
EosServiceWS();
public:
virtual ~EosServiceWS();
public:
void onFault();
xsd__string search(xsd__int Value0);
xsd__string suche(xsd__string Value0);
void test(); // ---
My test case
};
The class was generated from the WSDL file (like all server
side files).
I only tested the method test(), which has an empty body,
but I see a
constant increasing memory consumption which does not shrink.
Is it a known problem? on Windows? How about Linux?
Any hints to find a workaround are welcome.
Cheers Markus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]