Valerio,
I used only a single client. It is enough to run a single client for the banking example
to explode if the client initiates one transaction after another in a loop without any delay
in between. The tomcat server that runs the coordinator can quickly balloon over 200MB
and eventually crash with out-of-memory exception. With the workaround, its footprint
saturates at below 150MB and exhibits very good performance. The tomcat servers for
the initiator and participants are similar.
I run the coordinator, completion initiator, participants, and the client on different nodes.
Wenbing
I used only a single client. It is enough to run a single client for the banking example
to explode if the client initiates one transaction after another in a loop without any delay
in between. The tomcat server that runs the coordinator can quickly balloon over 200MB
and eventually crash with out-of-memory exception. With the workaround, its footprint
saturates at below 150MB and exhibits very good performance. The tomcat servers for
the initiator and participants are similar.
I run the coordinator, completion initiator, participants, and the client on different nodes.
Wenbing
----- Original Message
----
From: Valerio Vianello <[EMAIL PROTECTED]>
To: Wenbing Zhao <[EMAIL PROTECTED]>
Sent: Thursday, October 12, 2006 9:11:03 AM
Subject: Re: memory leakage?
From: Valerio Vianello <[EMAIL PROTECTED]>
To: Wenbing Zhao <[EMAIL PROTECTED]>
Sent: Thursday, October 12, 2006 9:11:03 AM
Subject: Re: memory leakage?
Hi Zhao,
How many clients have you used to test Kandula ?
and which enhancements have you noticed? after the correction.
thanks
Valerio
----- Original Message -----From: Wenbing ZhaoTo: Valerio VianelloSent: Wednesday, October 11, 2006 5:44 AMSubject: Re: memory leakage?You need to either import the CallbackRegistry class
(import org.apache.kandula.coordinator.CallbackRegistry;),
or use the fully qualified class name.
I inserted the remove() call before the notify() call.
As Dasarath pointed out, these fixes should be regarded as quick-and-dirty.
A better design is needed to both satisfy the WS-AT specification and to
avoid memory leaks.
Wenbing
----- Original Message ----
From: Valerio Vianello <[EMAIL PROTECTED]>
To: Wenbing Zhao <[EMAIL PROTECTED]>
Sent: Tuesday, October 10, 2006 7:14:10 AM
Subject: Re: memory leakage?
Hi ZhaoI fixed the code but when compile it I have same problem like this :...tor\at\AbstractParticipant.java:150: cannot resolve symbol
symbol : variable CallbackRegistry
location: class org.apache.kandula.coordinator.at.AbstractParticipant
CallbackRegistry.getInstance().remove(this);
^in the CompletionInitiatorCallback I must insert the code after notify() ?thanksValerio
