| View previous topic :: View next topic |
| Author |
Message |
Milos Guest
|
Posted: Tue Jun 28, 2005 3:43 pm Post subject: DCOM application server memory grow |
|
|
Hi all,
we have 3-thier application (database<->application server<->clients) using
Oracle, BDE and DCOM.
Approximately 40 clients.
Application server size grows constantly until it frezes . I presume that
some memory doesn't get free when clients disconnect from aplication server.
I run a simple test just start and stop client application and some memory
does not get free on application server (i examine memory with procexp
tool). I have checked the server code for any unfree memory (for example: if
i would forgot to free some stringlist in try - finally block) but haven't
found it.
Has anyone had similar expiriance?
Regards, Milos
|
|
| Back to top |
|
 |
Robert Schieck (TeamB) Guest
|
Posted: Wed Jun 29, 2005 11:31 pm Post subject: Re: DCOM application server memory grow |
|
|
Milos wrote:
| Quote: | Has anyone had similar expiriance?
|
It has been many years since I did this..... We used midas for it...
Are you careful to close your queries and database connections on your
middle tier ?
hth
--
Rob Schieck
TeamB
|
|
| Back to top |
|
 |
Milos Guest
|
Posted: Thu Jun 30, 2005 8:09 am Post subject: Re: DCOM application server memory grow |
|
|
Hi,
On Application server we have TDataBase property KeepConnection set to True.
I'am not sure how
remote data module handle threads.
Our client is an MDI form (exe) that on stratup connects to application with
TDCOMConnection.
Forms are fsMDIchild and are located in seperated dll-s. Main client
application starts dll-s. So each dll connects to application server.
When we close dll or main exe, we have event on destroy datamodule where we
iterate through components and if it's TClientDataSet then we close it. So
we close all connections on client before destroying it.
Does that close querys on application server ?
Regards Milos
<Robert Schieck (TeamB)> wrote
| Quote: | Milos wrote:
Has anyone had similar expiriance?
It has been many years since I did this..... We used midas for it...
Are you careful to close your queries and database connections on your
middle tier ?
hth
--
Rob Schieck
TeamB
|
|
|
| Back to top |
|
 |
Milos Guest
|
Posted: Mon Jul 04, 2005 7:36 am Post subject: Re: DCOM application server memory grow |
|
|
I have added on destroy remotedatamodule event where I close all querys
(TQuery), session (TSession) and connection to database (TDataBase), but the
server memory is still growing.
<Robert Schieck (TeamB)> wrote
| Quote: | Milos wrote:
Has anyone had similar expiriance?
It has been many years since I did this..... We used midas for it...
Are you careful to close your queries and database connections on your
middle tier ?
hth
--
Rob Schieck
TeamB
|
|
|
| Back to top |
|
 |
Robert Schieck (TeamB) Guest
|
Posted: Wed Jul 06, 2005 12:28 pm Post subject: Re: DCOM application server memory grow |
|
|
Milos wrote:
| Quote: | I have added on destroy remotedatamodule event where I close all
querys (TQuery), session (TSession) and connection to database
(TDataBase), but the server memory is still growing.
|
I really don't have any other ideas. With the BDE you did have to make
sure you commited the transaction, close the queries and close the
database connection.
IIRC they would have to reboot the midas server every couple of days.
--
Rob Schieck
TeamB
|
|
| Back to top |
|
 |
Paul McKenzie Guest
|
Posted: Thu Jul 14, 2005 1:07 am Post subject: Re: DCOM application server memory grow |
|
|
Robert Schieck (TeamB) wrote:
| Quote: | Milos wrote:
I have added on destroy remotedatamodule event where I close all
querys (TQuery), session (TSession) and connection to database
(TDataBase), but the server memory is still growing.
I really don't have any other ideas. With the BDE you did have to make
sure you commited the transaction, close the queries and close the
database connection.
IIRC they would have to reboot the midas server every couple of days.
We had memory issues with our AppServer (D7 development) the memory grew and we received |
"Out-Of-Memory" exceptions, before all memory was actually used.
One of the big fixes was using the D2005 Midas.dll.
|
|
| Back to top |
|
 |
|