cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laurent Medioni" <lmedi...@temenos.com>
Subject RE: thought I had fixe it
Date Tue, 25 Oct 2011 07:10:27 GMT
+ No1 potential memory leak ever: be sure to close your jdbc objects
whatever happens, provide catch blocks to close objects when
instantiations go wrong + make sure the close() methods are always
called at some point from your code (as soon as you have read the
resultSet).

But, as already said, storing large objects in continuations is a sure
recipe for failure ;)
You should configure the Continuation Manager with something like:
<continuations-manager logger="flow" session-bound-continuations="true"
time-to-live="3600000">
	<expirations-check type="periodic">
		<offset>180000</offset>
		<period>180000</period>
	</expirations-check>
</continuations-manager>
This will give continuations a time to live of 1 hour, which is probably
more than enough for replaying continuations if needed. And when the
session expires everything will be GCed, as soon as possible/needed...

Laurent

The information in this e-mail and any attachments is confidential and may be legally privileged.

It is intended solely for the addressee or addressees. Any use or disclosure of the contents

of this e-mail/attachments by a not intended recipient is unauthorized and may be unlawful.

If you have received this e-mail in error please notify the sender. 
Please note that any views or opinions presented in this e-mail are solely those of the author
and 
do not necessarily represent those of TEMENOS. 
We recommend that you check this e-mail and any attachments against viruses. 
TEMENOS accepts no liability for any damage caused by any malicious code or virus transmitted
by this e-mail.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message