Hi,

At December 5, 2004, 05:59, lgauton wrote:

> Further after assuming that wrapping TIB_Session creates, table
> prepares, table opens and now TIB_Session frees within a critical
> section cures the problem - it does not. The operation is better and
> load testing the application means we can have 500+connections(not
> concurrently, in total) before freezing occurs. We are currently
> investigating this.

It seems more like tuning the server, than anything else. Also, do
keep in mind that an ISAPI session will probably stay longer in memory
than what you are thinking and might be using resources. The default
connection timeout in IIS 5 is 15 minutes(900 seconds), so that
basically means that the ISAPI session related to one connection will
only be killed after 15 minutes of inactivity. This could probably
cause some of the problems that you are seeing.

If you haven't done so already, here's a link on MS Technet that would
be of interest:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/iis/maintain/optimize/iis5tune.mspx

You didn't mention which Windows version and IIS version you are
using. The above link is for IIS 5 on Windows 2000. If you are using
IIS 6 on Windows 2003, you should be able to find some tuning
information as well, by doing a search.

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)