From: Eric.Boyer at insa-toulouse.fr (Eric BOYER) Date: Mon, 19 Jun 2006 09:51:16 +0200 Subject: [Pljava-dev] java.lang.OutOfMemoryError In-Reply-To: <4492BB01.5060205@tada.se> References: <4492740D.4040302@insa-toulouse.fr> <4492BB01.5060205@tada.se> Message-ID: <44965774.7050203@insa-toulouse.fr> Thomas Hallgren a ?crit : >Eric, >You limit the postmaster to use 64M memory per session. > A session is a the trigger ? > That might be a >problem but it doesn't have to be. It all depends on what your server is >doing. I'm sure it's not the garbage collector (the first thing a JVM >does when it runs short of memory is to collect available garbage). > >You have to provide more information. The server log is generally far >more useful then the output from the client that you provided here. The >exact version of the PL/Java, PostgreSQL, and Java VM might be helpful >too. And of course, some hint of what you do when the error occurs. > >Common errors include storing tuple data in collections (and thereby >preventing them from being garbage collected). PL/Java 1.2 had a memory >leak that occured when you had functions that returned huge result sets. > > We use : Postgres 8.1 Pljava 1.2.0 jdk 1.4 Our server launch trigger which launch trigger, etc ... The treatment is long sometimes ... The java code is a big application which have to manage informations for an information system Eric >Regards, >Thomas Hallgren > > >Eric BOYER wrote: > > >>Hello >> >>We use pl java to launch an application >> >>org.postgresql.util.PSQLException: ERREUR: java.lang.OutOfMemoryError >> at >>org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1512) >> at >>org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1297) >> at >>org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188) >> at >>org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:437) >> at >>org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:339) >> at >>org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:331) >> >>We have a long treatment in a loop and the memory grow gradually up to a >>java.lang.OutOfMemoryError. >> >>What could be the problem ? >> >>- garbage collector ? >>- vmoptions ? : pljava.vmoptions = '-Xmx64M' >> >>Our serveur have 1Go RAM and postmaster start with a low consumption of >>RAM and grow up to ~300M ... >> >>Thanks for your help >> >>Eric >> >>_______________________________________________ >>Pljava-dev mailing list >>Pljava-dev at gborg.postgresql.org >>http://gborg.postgresql.org/mailman/listinfo/pljava-dev >> >> >> > >_______________________________________________ >Pljava-dev mailing list >Pljava-dev at gborg.postgresql.org >http://gborg.postgresql.org/mailman/listinfo/pljava-dev > > >