Hello All,
I built a web app (exe) w/database connectivity using Borland Delphi 7 and deployed it using IIS. However, IIS seems to be creating a separate instance for each web module accessed in the (most pages are separate delphi web modules with different functionality). These modules run in a virtual directory on IIS. After the application is exited and the browser is closed, the IIS instances remain. They keep piling up using about 5MB to 10MB of memory per instance. It requires a hard-boot to kill these instances.
FYI: WebModule.OnCreate sets the DB connection to active and the DBExpress Object Connected property is also set to True. WebModule.OnDestroy sets the dbExpress connection to false.
Could someone tell me what I need to do so the instances terminate once the user exits the application?
Environment: Windows 2000 Server with SP4, Oracle 9i db, IIS 5.0
Thank you,
VJ
I built a web app (exe) w/database connectivity using Borland Delphi 7 and deployed it using IIS. However, IIS seems to be creating a separate instance for each web module accessed in the (most pages are separate delphi web modules with different functionality). These modules run in a virtual directory on IIS. After the application is exited and the browser is closed, the IIS instances remain. They keep piling up using about 5MB to 10MB of memory per instance. It requires a hard-boot to kill these instances.
FYI: WebModule.OnCreate sets the DB connection to active and the DBExpress Object Connected property is also set to True. WebModule.OnDestroy sets the dbExpress connection to false.
Could someone tell me what I need to do so the instances terminate once the user exits the application?
Environment: Windows 2000 Server with SP4, Oracle 9i db, IIS 5.0
Thank you,
VJ