Good Day,
The SDK Help states the following definitions for each DI Server Configuration:
- DataConnectionTimeOut. Determines the time of inactivity (in minutes) after which the DI Server disconnects the user from the database (default: 15 minutes).
- DeadLockRetries. Determines the number of automatic retries when a 'dead lock' event occurs in the database (default: 3 retries).
- LogFile. Contains the absolute path name of the log file. The log file can include up to 100,000 lines. When a log file reaches its maximum line length, the DI Server renames it by adding a time stamp, and then creates a new log file.
- LogLevel. Determines the level of log: Error, Info or None. Error level is used for storing all fault messages. Info level is used for storing all the request and response messages.
- MaxDataConnections. Determines the maximum concurrent connections (default: 100).
- MinDataConnections. Determines the minimum concurrent connections (default: 2).
I have some questions for these specific configurations:
- DataConnectionTimeOut: when I open a connection and wait >15 minutes (Default value) I start doing transactions with the same session ID and it doesn't give me a disconnected user error or something of the sort. If what the SDK Help says is true, then why can I keep doing transactions with the same Session ID??. If the DataConnectionTimeOut doesn't work as it should, then how do you manage the open connections of the DI Server since after some time, the DI Server and my web application hangs???
- MaxDataConnections and MinDataConnections: I would like to know in depth how this property really works. Is there any documentation where I can have more information on how this property works.
Thank you for your help.
Antonio Burgos.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.