home list archives users mailing list

Subject: Re: OGSA-DAI system protection

Date view Thread view Subject view Author view Attachment view

From: Michael Sutter (Michael.Sutter@ipe.fzk.de)
Date: Apr 06, 2006 08:45

Thanks for your answer,

my container uses up to 512 MB memory and several other services are
deployed and uesd on it, e. g. Gram Service. After the error occured
only the OGSA-DAI service is affected. The Gram service is still
operational.

I think I don't do anything special with the OGSA-DAI service. I only
create a String which contains the SQL query and perform it over the
service. The source code looks like this:

String sqlQuery = "select name, date from mytable where ..";
SQLQuery query = new SQLQuery(sqlQuery);
WebRowSet rowset = new WebRowSet(query.getOutput());
ActivityRequest request = new ActivityRequest();
request.add(query);
request.add(rowset);
service.perform(request);
...

I don't create a session manually, but for my understanding of OGSA-DAI
a sesssion is created when the service performs my query. Isn't this right?

I can't tell you how many requests I can perform, but I thing it depends
of how many rows I retrieve from my request. Some requests I perform
have up to 700 rows in it and when I perform such request 4 or 5 times
I think the error occurs, but this isn't really reproducible. I don't
perform such requests successively, there are requests between which
contains only a few rows. Can the huge requests be the problem?

Regards Michael

Ally Hume wrote:
> Michael,
>
> It seems that OGSA-DAI is running out of memory. You could try to
> increase the memory allocated to the GT container but I suspect that
> will simply allow you to run for a little longer rather than genuinely
> solve the problem.
>
> Can you tell us what exactly what you are doing so we can attempt to
> reproduce this and hence diagnose it? What is the maximum memory you
> have allocated to the GT4 container? Are you running anything other
> than OGSA-DAI on this container?
>
> What perform documents are you sending to OGSA-DAI? Are you creating
> any sessions or anything else that would require state to be held in
> the server between requests?
>
> How many requests can you execute before this happens? Do you think
> it is a function of how many requests you execute or how many days the
> server has been running?
>
> Regards,
>
> Ally
>
> -------------------------------------------------------------
> Ally Hume
> Software Architect
> EPCC, University of Edinburgh
> James Clerk Maxwell Building
> Mayfield Road E-mail: a.hume@epcc.ed.ac.uk
> Edinburgh, EH9 3JZ Phone: + 44 (0) 131 651 3397
> United Kingdom Fax: + 44 (0) 131 650 6555
> -------------------------------------------------------------
>
>
> -----Original Message-----
> From: owner-users@ogsadai.org.uk [mailto:owner-users@ogsadai.org.uk]
> On Behalf Of Michael Sutter
> Sent: 05 April 2006 14:16
> To: users@ogsadai.org.uk
> Subject: OGSA-DAI system protection
>
> Hello all,
>
> I have a problem when using OGSA-DAI WSRF 2.1 under GT 4.0.1
> container.
> After starting the container everything works fine when using the
> SQLQuery Activity. The problem is, when running the server several
> days
> and query the database over OGSA-DAI several times I always get a
> OGSA-DAI system protection exception as shown below. The only way to
> get
> OGSA-DAI working is stopping and restarting the GT4 container. After
> restart everything works fine again, with equal SQL queries I used
> when
> I got the system protection exception, so the SQL queries are right.
> The
> same error occurs when using OGSA-DAI several times after restart, but
> i
> can't reproduce when the error appears.
>
> I don`t know why this happens, if anybody has a idea please tell it to
> me.
>
> Thanks and Regards
> Michael
>
> 2006-04-05 12:49:34,410 ERROR common.MemoryUtilities
> [Thread-2598,<init>:36] OGSA-DAI system protection: Adding 0 bytes to
> the Java stack may cause a java.lang.OutOfMemoryError
> uk.org.ogsadai.common.exception.common.CommonSystemException: OGSA-DAI
> system protection: Adding 0 bytes to the Java stack may cause a
> java.lang.OutOfMemoryError
> at
> uk.org.ogsadai.common.MemoryUtilities.checkMemory(MemoryUtilities.java
> :159)
> at
> uk.org.ogsadai.common.MemoryUtilities.checkMemory(MemoryUtilities.java
> :59)
> at uk.org.ogsadai.activity.Activity.process(Activity.java:333)
> at
> uk.org.ogsadai.activity.RequestProcessor.processActivity(RequestProces
> sor.java:107)
> at
> uk.org.ogsadai.activity.RequestProcessor.process(RequestProcessor.java
> :76)
> at
> uk.org.ogsadai.activity.ActivityPipelineRequestComponent.process(Activ
> ityPipelineRequestComponent.java:107)
> at
> uk.org.ogsadai.engine.controlflow.FlowRequestComponent.process(FlowReq
> uestComponent.java:73)
> at
> uk.org.ogsadai.activity.ActivityRequest$1.run(ActivityRequest.java:306
> )
> 2006-04-05 12:49:34,412 ERROR activity.Activity
> [Thread-2598,<init>:148] OGSA-DAI system protection: Adding 0 bytes to
> the Java stack may cause a java.lang.OutOfMemoryError
> 2006-04-05 12:49:34,413 ERROR activity.Activity
> [Thread-2598,setError:390] Error processing activity
> ogsadai-10a69a9edb1 (uk.org.ogsadai.activity.ResultActivity) :
> OGSA-DAI system protection: Adding 0 bytes to the Java stack may cause
> a java.lang.OutOfMemoryError
>
>
>
>
>



Date view Thread view Subject view Author view Attachment view