Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
FOXISAPI-loaded COM objects staying in mem for weeks?
Message
General information
Forum:
Visual FoxPro
Category:
Internet applications
Miscellaneous
Thread ID:
00308398
Message ID:
00308517
Views:
33
>>We are designing a web extension to an application (using foxisapi or rick
>>Does anyone experienced a FOXISAPI COM DLL or EXE staying quietly in NT4 memory for weeks without a halt... No reloading, no crash.
>>
>>We have no experience - just some crash tests here - and a few doubts about persistent.
>
>
>I have a number of apps that run for months without user access to the server.
>
>However, FoxISAPI has no mechanism for crash recovery. If it goes down the
>server is hung and things are off.
>
>Web Connection is the only tool I know of that monitors its running servers
>for timeouts and also catches exceptions and reloads servers automatically
>if hung.
>
>In addition you can remotely configure and administer servers and update
>code online without shutting the server down.

Hi Rick,

Thank you for getting in at this stage. The pb we are running in now is the following :

1) we load the object on-line - it gets into the memory - the server answer a dummy "not available - call later",
2) we start the object - providing odbc db-engine username + password.
At this stage the object takes a few minutes to load sql-pt cursors. The object is active ready to distribute info from its temp cursors (no db connection).

This method provides us with ultimate security control - required for this project - as data remain in native sql-db format (sybase)- and ultimate speed - as data is provided from sql-pt cursors closed when object is released.

Great... no odbc connection string embedded in code nor download into relatively unsecure db formats. We really like this approach.

After a period a time(a few minutes, <g>the isapi server clearly unload this object. The server reload automatically but it is not active. All cached data have been release. It is in a "not available - call later" state.

I clearly found no trick to prevent foxisapi to unload this dammed com object. the foxisapi /status say the object is there in cache but it is actually released (:

We need support for this very heavy stateful object. Does west-wind connection provide this ability to lock the object in memory ? I am really willing to try your software.
By the way your book has been an outstand support to us. Thank you for taking the time to write it. Great stuff and another reason to stick to vfp!
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform