EXP Computer ThinConnect4 Uživatelská příručka stáhnout pdf (Strana 114)

"jdbc:rdbNative:my_db_dir:pers@ignoreStatementCancel=true",

user, pass);

8.8 Inactivity timeouts

The amount of time either a client connection or a server may remain inactive before being

forcibly terminated may be set using server and connection switches.

8.8.1 Client connection timeout

The –cli.idleTimeout switch may be used to specify the amount of time in milliseconds that

a connection may remain inactive before being closed down. The default value of 0 specifies

that the time is indefinite, i.e. the connection will not timeout.

You may specify the client 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 –cli.idleTimeout 3600000

specifies that any client connection may remain idle for 1 hour before being terminated

or in the Xml-formatted configuration file :

<server

name="srv2forRdb"

type="RdbThinSrv"

url="//localhost:1708/"

cli.idleTimeout="3600000"

When a client is forcibly terminated by this timeout the following message will be logged in

the server log:

oracle.rdb.jdbc.common.RdbException: Client terminated

due to inactivity

When specified as a server switch, the timeout will apply to all clients connected using that

server.

You may also specify the client timeout as a qualifier on the connection string on the client-

side application.

114

1 2 ... 109 110 111 112 113 114 115 116 117 118 119 ... 162 163

Žádné komentáře

EXP Computer ThinConnect4 Uživatelská příručka Strana 114