Hi
I posted similar question couple of weeks ago.
I tried with tools that could detect memory leaks and I get hints about using
noncompatible commands for allocating memory (using operator new for allocating
and then free for dealocating). I checked the source code and I find no such
case
ct is created
inside callback function is also destroyed when the function returns. This means
that HTTPChannel.dll will be called multiple times.
Is it possible to avoid multiple calls of loading
library in multithreaded environment?
Best regards
Tomaz Rotovnik
TRING:
if
(AxisEngine::m_bServer){delete
[]
const_cast(m_Value.pStrValue); } break; ...
}
So allocated memory is only deleted when Axis is
initialized as server. Why? With commenting this condition string data type is
deleted with no memory leak.
Is this wrong?
Best reg
Hi again
I'm trying to solve the problem with the memory
leak on the client side of axis library.
I've next function which is called in multithreaded
way:
setReturnAddPointsParameter* pRAPP = NULL;MPBLPSoap
pBLP_authorize(sMPG.strURL.c_str(),
APTHTTP1_1);pBLP_authorize.Timeout(10);pRA
> which you can find
in setReturnAddPointsParameter.cpp.>> I haven't been looking at
XSD_DOUBLE etc but if you say that> these are created with new you are
probably correct.>> /Anders>>>From: Tomaz
Rotovnik <[EMAIL PROTECTED]>>>Reply-To: "Apache AXIS C User List
Hi
You can also set Working directory in VS. Open menu
Projects->Settings->Debug tab ->Working Directory
In that directory than put all dll's needed for the
project.
Best regards
Tomaz
- Original Message -
From:
Pico
Florin
To: Apache AXIS C User List
Sent: Th
not deleted.
I have been requested to do a svn patch but as I am not
working on the lastest version I have not found the time to do
this. I will do it as soon as I can...
/Anders
From: "Tomaz Rotovnik" <[EMAIL PROTECTED]>
Reply-To: "Apache AXIS C User List"
To: &quo
Hi
I'm using axis 1.5 C++. When I tested my client (multithreaded) I found out that memory is
growing with number of transactions. I read Axis C++ Memory Management Guide
about De-allocation Semantics.
For example WSDL2XML generated this parts of
code
Parameters that will be send over t
r that the response content is maybe changed(but
why?).
Regards,
Florin
Tomaz Rotovnik <[EMAIL PROTECTED]>
wrote:
I think the problem could be in requesting
different parameters than those that are sent as response. I mean in
(_responseHeader.getCh
I think the problem could be in requesting different
parameters than those that are sent as response. I mean in (_responseHeader.getChars() you have defined something else that is realy
returned.
Tomaz
- Original Message -
From:
Pico
Florin
To: Apache AXIS C User Lis
Hi
I think I have the same problem. If you use original (you didn't compiled
it) AxisXMLParserXerces.dll the name of xerces should be xerces-c_2_2_0.dll.
Other way it is possible to get the following error. You can also try to
compile AxisXMLParserXerces.dll by yourself wih newer version of x
gt;initialize(CPP_RPC_PROVIDER))" fails?
Hmm, not quite clear on what
you're saying here but if it helps I don't think we fixed the transport reload
issue until post 1.5
"Tomaz Rotovnik" <[EMAIL PROTE
Hi
I tested again and I think I found the problem.
First I used my compiled version of AxisClient.dll with AxisXMLParser.dll
allready provided in axis version 1.5 + xerces-c_2_2_0. Each time I performed
transaction, the HTTPChannel.dll librariy was loaded again and again.
Then I used my
Hi
When I use multithreading on client side I found out that for each
transaction HTTPChannel.dll library is loaded. Is this necessary? Why only
this dll and not also AxisXMLParser and HTTPTransport?
Best Regards
Tomaz
Hi
I don't have problems with calling Axis::terminate(). But I call it after all Axis
instances are already destroyed.
- Original Message -
From:
Pico
Florin
To: Apache AXIS C User List
Sent: Tuesday, October 11, 2005 3:35
PM
Subject: Re: Why
"m_pCall->in
Hi
You need to include Axis.hpp in the main
file.
If I'm not wrong than you should call
Axis::initialize(false); before you use axis objects. In my example I call
this in my main loop before I created threads in which I created pBLP = new
Soap(s.strURL.c_str(), APTHTTP1_1);
When all th
where this happens.
Thank you
Tomaz
- Original Message -
From: "Samisa Abeysinghe" <[EMAIL PROTECTED]>
To: "Apache AXIS C User List"
Sent: Monday, October 10, 2005 3:51 PM
Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
he AXIS C User List"
Sent: Saturday, October 08, 2005 12:25 AM
Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
Tomaz Rotovnik wrote:
Hi
I've the same problem. Couple of days ago I send question about safe
threading on client side. When I start debugging
Hi
I've the same problem. Couple of days ago I send
question about safe threading on client side. When I start debugging I found out
that call m_pCall->initialize(CPP_DOC_PROVIDER)) causes
exception.
Then I enable possibility (uncomment) to print
out possible exceptions in function Call
Hello
I'm looking for some information's about running
multiple calls in client side of axis. I'm using axis version 1.5. The
problem is that when I call function again before it returns (in
different thread) it returns exception when calling invoke
method.
In main loop there is call t
20 matches
Mail list logo
