Hi Jorge,
>> Is that the "Session Timeout" number set at the Advanced tab?
no, that is for the Session Timeout, not the Connection timeout.
The two have (quite literally) nothing to do with each other.
>> It was setting by code to 90001 cents. of sec, or about 15 minutes, but I did tests of server heavy loading and caused problems (server collapsing),
The length of the session timeout should have very little impact on server work-load, so it would be interesting to duplicate the test you set up in this regard. I expect there is something else in play here - perhaps memory limits - but for API calls interaction with the session is minimal.
<< However, from time to time the server simply stops responding, although the program is still working.
This suggests that either
a) you are leaking threads, and hit the thread max (see log window to see if the thread being assigned to incoming requests is returning to 3 after quiet spells). or
b) you have a bug in your code which is causing the server to be "blocked" - usually the incorrect use of a critical section, or incorrect use of prop:sql, or something like that.
c) You are using a SQL database and the clarion Exe is losing the connection to the database.
>> A processMonitor analisys show a lot of "connections" closing at that time, so we were wondering if it could be related.
Incoming connections will close, so if they are not being responded to you will see them closing.
Also - on the "Performance" tab there is a whole slew of numbers that gives you cluess as to what might be high when the program stops responding. Perhaps take a look at that?
cheers
Bruce