User guide

Connection conn = DriverManager.getConnection(
"jdbc:rdbthin://bravo:1701/my_db_dir:[e-mail]=36000
00",user, pass);
When specified this way the timeout will only apply to this one connection.
If a non-zero cli.idleTimeout is specified in both the server configuration and as a connection
qualifier, the lesser of the two values will be used for that connection.
Inactivity is determined by the lack of activity on the socket the server is listening to the
client on, if no request is sent from the client for the specified amount of time, a timeout is
deemed to have occurred.
If a client inactivity timeout occurs on a connection that is using a Multi-Process server
executor, that executor will be terminated. Even though the connection will be correctly
closed down after the timeout event, as it is unknown why there was no activity seen on the
connection, the executor sub-process is deemed "unsafe" and consequently is terminated.
8.8.2 Server Inactivity Timeout
You can specify the amount of time that a server may remain idle before being closed down
due to inactivity.
The –srv.idleTimeout switch may be used to specify the amount of time in milliseconds that
a server may remain inactive before being closed down. The default value of 0 specifies that
the time is indefinite, i.e. the server will not timeout.
You may specify the server idle timeout as a server configuration option either in the server
definition within an XML-formatted configuration file or as a command-line switch when
starting a server.
Example
For example:
$ java -jar rdbthinsrv.jar –port 1701 –srv.idleTimeout 3600000
specifies that the server may remain idle for 1 hour before being terminated
Or in the Xml-formatted configuration file :
<server
name="srv2forRdb"
type="RdbThinSrv"
url="//localhost:1708/"
srv.idleTimeout="3600000"
/>
115