Memory leaks due to retained qqcm_ExternalConnectionobjects
Hi Forte users,
Our server partition is accepting inbound External Connections through
the Forte ExternalConnection class.
Although our 4GL objects are properly garbaged, the
qqcm_ExternalConnection
are retained in memory, after the client closed the connection,
eventually
causing a memory leak (even if we take care to explicitly close() the
inbound
connection).
Has anyone run into this problem before ?
Thanks,
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]
[763 byte] By [
] at [2007-11-25 5:01:44]
Vincent,
We had this problem when we were working with Forte R2. ExternalRef class
can help. In R3 this memory leak is seem to be fixed.
Regards,
Mikhail Schelkin
Conextions, Inc.
misha@conextions.com
Vincent R Figari wrote:
> Hi Forte users,
>
> Our server partition is accepting inbound External Connections through
> the Forte ExternalConnection class.
> Although our 4GL objects are properly garbaged, the
> qqcm_ExternalConnection
> are retained in memory, after the client closed the connection,
> eventually
> causing a memory leak (even if we take care to explicitly close() the
> inbound
> connection).
>
> Has anyone run into this problem before ?
>
> Thanks,
>
> 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:21:37 >
