Great job guys
-- dims
On Fri, 14 Jan 2005 17:01:25 -0800, Lyndon Tiu <[EMAIL PROTECTED]> wrote:
> V D wrote:
>
> >
> > I reported it at:
> >
> > http://issues.apache.org/jira/browse/AXIS-1765
>
>
> Please give credit where credit is due.
>
> I found this issue but it was my colleagu
V D wrote:
I reported it at:
http://issues.apache.org/jira/browse/AXIS-1765
Please give credit where credit is due.
I found this issue but it was my colleague Malcolm Walker of Latitude
Geographics Group Ltd. who found the fix. If there is anywhere in the
bug report to put this, please do so. He
I reported it at:
http://issues.apache.org/jira/browse/AXIS-1765
Tim K. (Gmane) wrote:
Can you please file a bug for this at:
Can you please file a bug for this at:
http://issues.apache.org/jira/
for project Axis
Thanks.
Tim
Vy Ho wrote:
That does it. The memory no longer go up. The way I do it is inside
the generated stub, I wrap the call with a try/catch/finally, and in
that, I put your code below. I am not sure if
That does it. The memory no longer go up. The way I do it is inside
the generated stub, I wrap the call with a try/catch/finally, and in
that, I put your code below. I am not sure if this is the best way of
doing it. However, I am just testing. I won't use this code though.
In client-side s
WAJSBERG Julien RD-BIZZ wrote:
Vy Ho a écrit :
In client-side stub code, look for the call object and try:
Call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();
--
Lyndon Tiu
I can choose not to use the application scope for now. However, this
shows a very seri
Vy Ho a écrit :
In client-side stub code, look for the call object and try:
Call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();
--
Lyndon Tiu
I can choose not to use the application scope for now. However, this
shows a very serious problem with the generated
In client-side stub code, look for the call object and try:
Call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();
--
Lyndon Tiu
I can choose not to use the application scope for now. However, this
shows a very serious problem with the generated stub I believe.
Vy Ho wrote:
When setting the scope of my service to application, the client side
will run out of memory after 5-10 thousand hits. The service object on
the server side is thread safe and works with both application and
request scope. The server does not have any leak.
The reason I change it t
When setting the scope of my service to application, the client side
will run out of memory after 5-10 thousand hits. The service object on
the server side is thread safe and works with both application and
request scope. The server does not have any leak.
The reason I change it to application
10 matches
Mail list logo
