Integer (minutes)
0
Purpose
The ConnectionTimeout parameter specifies the maximum number of minutes that the application server waits for activity (messages sent by or received) from any client application attached to the server before the application session times out that client. Notification and timer traffic is ignored when determining if the connection has timed out.
If no activity occurs within the specified time, the application thread for that client terminates and the following message is displayed in a message box on the presentation client.
The current Application session timed out
The default value of zero (0) indicates that there is no timeout.
In addition, if the EnableAppRestrictions parameter in the [JadeAppServer] section is set to true, you can use the AllowSchemaAndApp<n> parameter to specify a timeout period for a specific schema and optional application, by using the following parameter syntax.
AllowSchemaAndApp<number> = schema‑name [, application‑name], timeout‑value
The following example shows setting the timeout value in the MyApp application in the MySchema schema to 30 minutes.
[JadeAppServer] ConnectionTimeout = 0 EnableAppRestrictions = true AllowSchemaAndApp1 = JadeSchema AllowSchemaAndApp2 = MySchema, MyApp, 30
The parameter settings shown in this example allow all JadeSchema applications to be run without any timeout and the MyApp application in the MySchema schema to time out if no activity occurs within 30 minutes.
When an application times out (that is, the period specified in the ConnectionTimeout parameter elapses without activity), the equivalent of a monitor force-off is performed, closing all forms and signing off without calling any methods.
Parameter is read when …
The application server node is next initialized; for example, when you restart the application server.