Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
jvx:communication:timeouts [2018/02/01 10:27] admin |
jvx:communication:timeouts [2020/07/08 17:47] (current) cduncan articles |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~Title: Configuring Timeouts~~ | ~~Title: Configuring Timeouts~~ | ||
| - | For security reasons, the validity of client/server connections or sessions is limited. After inactivity (no user interaction) of a predefined time period the connection or session is invalidated and the client has to reconnect if necessary. If no timeouts are defined for JVx, the connections/sessions are not invalidated. | + | For security reasons, the validity of client/server connections or sessions is limited. After inactivity (no user interaction) of a predefined time, the connection or session is invalidated, and the client has to reconnect if necessary. If no timeouts are defined for JVx, the connections/sessions are not invalidated. |
| Timeouts can be defined in the following ways: | Timeouts can be defined in the following ways: | ||
| Line 11: | Line 11: | ||
| == All Applications == | == All Applications == | ||
| - | Multiple applications can be in use on a server; it is therefore possible that timeouts are set for all of a server´s applications. The server configuration is handled by the file //config.xml// in the server directory (///rad/server//). | + | Multiple applications can be in use on a server; it is, therefore, possible that timeouts are set for all of a server´s applications. The server configuration is handled by the file //config.xml// in the server directory (///rad/server//). |
| Timeouts are defined as follows: | Timeouts are defined as follows: | ||
| Line 47: | Line 47: | ||
| </file> | </file> | ||
| - | The example does not define a timeout for the subsession. The timeout for the SubSession is therefore based on the server configuration. | + | The example does not define a timeout for the subsession. The timeout for the subsession is based on the server configuration. |
| == Per Connection/Session == | == Per Connection/Session == | ||
| Line 63: | Line 63: | ||
| </file> | </file> | ||
| - | <fs 20px>Notice</fs> | + | \\ |
| + | **<fs 20px>Notice</fs>** | ||
| - | If the Master Connection is not used, because you only communicate via a Sub Connection, the Master Connection remains active. The activity of the Sub Connection is also counted as activity in the Master Connection. | + | If the master connection is not used, because you only communicate via a sub connection, the master connection remains active. The activity of the sub connection is also counted as activity in the master connection. |
| - | It's also possible to configure the timeout in seconds. Simply use following key: | + | It's also possible to configure the timeout in seconds. Simply use the following key: |
| <file xml> | <file xml> | ||