On Fri, Mar 5, 2010 at 5:51 AM, Samisa Abeysinghe wrote:
>
>
> On Fri, Mar 5, 2010 at 2:29 AM, Hatim Daginawala
> wrote:
>>
>> First of all let me say, I did not mean to offend anyone, undermine the
>> work you do or even complain. If I did, I am sorry.
>
> Sure, I was purely trying to make sure
On Fri, Mar 5, 2010 at 2:29 AM, Hatim Daginawala <
hatim.daginaw...@argodata.com> wrote:
> First of all let me say, I did not mean to offend anyone, undermine the
> work you do or even complain. If I did, I am sorry.
>
Sure, I was purely trying to make sure that other users do not misunderstand
a
If you are using custom HTTP headers and seeing leaks, let me know. I will
write a small test program to demonstrate how I do it. It's a little complex to
just write it up.
-Original Message-
From: Olivier Mengué [mailto:omen...@oxymel.com]
Sent: Thursday, March 04, 2010 11:07 AM
To: Ap
First of all let me say, I did not mean to offend anyone, undermine the work
you do or even complain. If I did, I am sorry.
Axis is great product and I am using axis2c in a production environment and I
am very grateful. Thank you.
The reason I say it's not designed for reuse it precisely bec
On Thu, Mar 4, 2010 at 9:51 PM, Hatim Daginawala <
hatim.daginaw...@argodata.com> wrote:
> No harm in trying. I have been using release 1.5 for over a year now in a
> very high volume environment.
>
>
>
> svc_client is not designed to be reused.
>
This is an incorrect statement. We reuse it, and
Hatim Daginawala wrote:
>No harm in trying. I have been using release 1.5 for over a year now in a very
>high volume environment.
I wanted to avoid to call svc_client_create() for every call because it seems
this is where axis2.xml is parsed, dynamic libraries loaded... SOAP is heavy
enough, I
No harm in trying. I have been using release 1.5 for over a year now in a very
high volume environment.
svc_client is not designed to be reused. Here are some of the issues I came
across in 1.4/1.5
- It leaks all over the place - For example HTTP headers, you will
have to reset all
On Thu, Mar 4, 2010 at 8:37 PM, Hatim Daginawala <
hatim.daginaw...@argodata.com> wrote:
> You probably need to call axiom_node_free_tree on both request and
> response node before reusing svc_client
>
I do not think so - this will lead to seg faults if I recall right.
If you cannot share the c
You probably need to call axiom_node_free_tree on both request and response
node before reusing svc_client
From: Olivier Mengué [mailto:omen...@oxymel.com]
Sent: Thursday, March 04, 2010 8:36 AM
To: Apache AXIS C User List; Apache AXIS C User List
Cc: Axis2/C user
Subject: RE : How to fix mem
Samisa Abeysinghe wrote:
>It is hard to tell from the list of methods given. Can you please provide
>the code you are using to test? Then we can profile and see where the leaks
>are.
As you probably expected, no, I can't.
Could you at least tell me if I have a good understanding of the API?
Is i
It is hard to tell from the list of methods given. Can you please provide
the code you are using to test? Then we can profile and see where the leaks
are.
Samisa...
2010/3/4 Olivier Mengué
> Hi,
>
> I have an Axis2/C client that does multiple calls to the same web service.
> So I'm reusing the
Hi,
I have an Axis2/C client that does multiple calls to the same web service.
So I'm reusing the same axis2_svc_client object.
The WSDL was too complex for the WSDL code generator, so I had to create the
code myself.
The client call works fine.
However my problem is I have a memory leak in ever
12 matches
Mail list logo
