Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <419C8E6D.1010004@apache.org>
Date: Thu, 18 Nov 2004 12:58:37 +0100
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Pesky memory problems (Tomcat/WindowsXP)
References: <5E091A68F794974CAF431CA31F5AF2CC11E9B7@server.bizzdesign.nl>
In-Reply-To: <5E091A68F794974CAF431CA31F5AF2CC11E9B7@server.bizzdesign.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bart Molenkamp wrote:
>>Two "usual suspects" are Cron jobs calling pipelines and macros in
>>JXTemplate.
>>
> 
> 
> I've had problems calling pipelines from Cron jobs. These caused
> OutOfMemoryErrors. Could you explain why, or even better, how to solve
> it?

If I know it I would solve it ;-) I wrote this because I remember some people 
having memory problems with it.

> 
> In my case, one Cron job that runs once every night sends mail to users.
> About 110 users, so a pipeline is called 110 times (to generate the mail
> content for every user). I use flowscript in that specific pipeline, and
> I guess that there are 110 continuations stored in memory all at once...

Hmmm, maybe you are right here and every pipeline call creates a new session 
with a new flowscript context. Multiplied with 110 this could really lead to a 
rather high memory consumption.

Two thoughts: Maybe you can create only one job sending all mails. Second, it 
would be interesting to profile the application (OptimizeIt, ...) and monitor 
how many Flowscript contexts are created.


-- 
Reinhard

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