From: | Eric(dot)Boyer at insa-toulouse(dot)fr (Eric BOYER) |
---|---|
To: | |
Subject: | [Pljava-dev] java.lang.OutOfMemoryError |
Date: | 2006-06-27 13:38:14 |
Message-ID: | 44A134C6.5030003@insa-toulouse.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
Hello,
we use now pljava 1.3 and postgres 8.1.4
we can't use java 1.5 because it depends on xmlrpc 3 which is an alpha
version.
The problem is still there.
We have a big treatment and after a long time, we have this outOfMemory.
We print the warning on the statement :
ERROR - ====>org.postgresql.pljava.internal.ServerException:
java.lang.OutOfMemoryErrorjava.lang.OutOfMemoryError
INFO - Statement WarningWARNING: buffer refcount leak: [779]
(rel=1663/16440/52989, blockNum=3, flags=0x27, refcount=1 2)
What could be this buffer refcount leak.
Is the "buffer refcount leak" the cause of the OufOfMemoryError or its
consequence ?
This long treatment is OK if we have the option : -Xmx512M
If we use -Xmx8M, it crash more quickly !
Thanks for your help
Eric
Thomas Hallgren a ?crit :
> Eric BOYER wrote:
>
>> Thomas Hallgren a ?crit :
>>
>>> Eric,
>>> You limit the postmaster to use 64M memory per session.
>>>
>> A session is a the trigger ?
>>
> No, a session is a connection to the database.
>
>> 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 ...
>>
> I would recommend three things.
>
> 1. Upgrade your Java to a 1.5.0_07 version. It performs much better
> from a memory consumption perspective.
> 2. Updgrate to PL/Java 1.3.0
> 3. If that doesn't help, try -Xmx128M.
>
> Regards,
> Thomas Hallgren
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hallgren | 2006-06-27 14:03:05 | [Pljava-dev] java.lang.OutOfMemoryError |
Previous Message | Thomas Hallgren | 2006-06-27 08:28:20 | [Pljava-dev] Tests fails |