BinaryData, DBSessions and memory leaks...
Hi Everyone,
We have memory leaks on the server partition when retrieving Blobs
from an Oracle DB through BinaryData objects. Although we took care
of using the ReleaseDistRef() on anchored objects, the
<large non-objects> item of the memory dump keeps growing and
growing until the garbage collector can not reclaim enough memory
and aborts the partition.
Has anyone run into this kind of problem before ?
Does anyone know exactly what this <large non-objects> is ?
Thank You for your help,
Vincent Figari
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at <a href=
"http://www.juno.com">http://www.juno.com</a>
Or call Juno at (800) 654-JUNO [654-5866]
[847 byte] By [
] at [2007-11-25 5:02:14]
Hi Vincent...
I think that Jimmy's response probably answered your main question (how
can you solve your memory issues), but I wanted to try to define (as
best I can) Large Non-Objects in Forte.
Large Non-Objects in Forte are any non-object reference above 1K in
size, including the string data associated with a text data, DB query
buffers (DBStatement handles, for example), and array container
objects.
I hope this helps...
-Katie
Vincent R Figari wrote:
>
> Hi Everyone,
>
> We have memory leaks on the server partition when retrieving Blobs
> from an Oracle DB through BinaryData objects. Although we took care
> of using the ReleaseDistRef() on anchored objects, the
> <large non-objects> item of the memory dump keeps growing and
> growing until the garbage collector can not reclaim enough memory
> and aborts the partition.
>
> Has anyone run into this kind of problem before ?
> Does anyone know exactly what this <large non-objects> is ?
>
> Thank You for your help,
>
> Vincent Figari
>
>
> You don't need to buy Internet access to use free Internet e-mail.
> Get completely free e-mail from Juno at <a href=
"http://www.juno.com">http://www.juno.com</a>
> Or call Juno at (800) 654-JUNO [654-5866]
--
**************************************************
Katie Carty
Senior Consultant
Forte Software, Inc.
<a href="http://www.forte.com">http://www.forte.com</a>
4801 Woodway Drive, Suite 300E
Houston, Texas 77056
vmail: (510) 986-3802
email: kcarty@forte.com
**************************************************
at 2007-6-29 9:22:54 >
Thank You Katie and Jimmy,
Indeed most of our statements were static embedded SQL, but the
few dynamic ones were eating up the memory at a fast pace.
The RemoveStatement() solved the problem.
Thank You again,
Vincent
On Wed, 18 Feb 1998 12:24:45 -0600 Katie Carty <kcarty@forte.com> writes:
>Hi Vincent...
>
>I think that Jimmy's response probably answered your main question
>(how
>can you solve your memory issues), but I wanted to try to define (as
>best I can) Large Non-Objects in Forte.
>
>Large Non-Objects in Forte are any non-object reference above 1K in
>size, including the string data associated with a text data, DB query
>buffers (DBStatement handles, for example), and array container
>objects.
>
>I hope this helps...
>
>-Katie
>
>
>
>
>Vincent R Figari wrote:
>>
>> Hi Everyone,
>>
>> We have memory leaks on the server partition when retrieving Blobs
>> from an Oracle DB through BinaryData objects. Although we took care
>> of using the ReleaseDistRef() on anchored objects, the
>> <large non-objects> item of the memory dump keeps growing and
>> growing until the garbage collector can not reclaim enough memory
>> and aborts the partition.
>>
>> Has anyone run into this kind of problem before ?
>> Does anyone know exactly what this <large non-objects> is ?
>>
>> Thank You for your help,
>>
>> Vincent Figari
>>
>>
>
>> You don't need to buy Internet access to use free Internet e-mail.
>> Get completely free e-mail from Juno at <a href=
"http://www.juno.com">http://www.juno.com</a>
>> Or call Juno at (800) 654-JUNO [654-5866]
>
>--
>**************************************************
>Katie Carty
>Senior Consultant
>Forte Software, Inc.
><a href="http://www.forte.com">http://www.forte.com</a>
>
>4801 Woodway Drive, Suite 300E
>Houston, Texas 77056
>
>vmail: (510) 986-3802
>email: kcarty@forte.com
>**************************************************
>
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at <a href=
"http://www.juno.com">http://www.juno.com</a>
Or call Juno at (800) 654-JUNO [654-5866]
at 2007-6-29 9:22:54 >
Hi Vincent,
Are you using dynamic queries to access the Oracle DB?.
If so, make sure you are using the following method at the end of your
queries :
self.Session.RemoveStatement(statementHandle=dynStatement);
,this will deallocate all the memory used during a particular query.
Otherwise, your <large-non-objects> will keep on growing. If this is
your case, your problems with memory usage will disappear.
Another reason of that "parameter" is that there are "server" operations
that were copied over to the client and are being "run" from within the
client across the network.
Jimmy Chung
Project Leader
GMD S.A.
Lima, Peru
> -
> From: v.figari@juno.com[SMTP:v.figari@juno.com]
> Sent: Miércoles 18 de Febrero de 1998 8:49 AM
> To:kamranamin@yahoo.com
> Subject:BinaryData, DBSessions and memory leaks...
>
> Hi Everyone,
>
> We have memory leaks on the server partition when retrieving Blobs
> from an Oracle DB through BinaryData objects. Although we took care
> of using the ReleaseDistRef() on anchored objects, the
> <large non-objects> item of the memory dump keeps growing and
> growing until the garbage collector can not reclaim enough memory
> and aborts the partition.
>
> Has anyone run into this kind of problem before ?
> Does anyone know exactly what this <large non-objects> is ?
>
> Thank You for your help,
>
>
> Vincent Figari
>
>
> You don't need to buy Internet access to use free Internet e-mail.
> Get completely free e-mail from Juno at <a href=
"http://www.juno.com">http://www.juno.com</a>
> Or call Juno at (800) 654-JUNO [654-5866]
>
at 2007-6-29 9:22:54 >
