...
| Info |
|---|
| title | Example - Setting the maximum number of connections for Sybase IQ |
|---|
|
| Code Block |
|---|
| $ mzsh topo set topo://container:<container>/pico:<pico name>/val:config.properties.sybase.iq.pool.maxlimit 20 |
|
By default, there is no timeout value defined for the socket tied to a database connection. This means that a running query could get stuck, in case the database suddenly becomes unreachable. To specify a timeout valueThere are two properties available for handling timeout of socket connections and socket threads:
sybase.jdbc.socketread.timeout with default value 180000 (3 minutes in milliseconds)
sybase.jdbc.socketconnect.timeout with default value 30000 (30 seconds in milliseconds)
To specify other timeout values, in milliseconds, set the Execution Context property sybase.jdbc.socketread.timeout in properties in the relevant <pico>.conf file.
| Info |
|---|
| title | Example - Setting the timeout for a socket tied to a Sybase IQ connection |
|---|
|
| Code Block |
|---|
| $ mzsh topo set topo://container:<container>/pico:<pico name>/val:config.properties.sybase.jdbc.socketread.timeout 600000
$ mzsh topo set topo://container:<container>/pico:<pico name>/val:config.properties.sybase.jdbc.socketconnect.timeout 20000 |
|
| Note |
|---|
|
When using the timeout property you must ensure that you set a limit that exceeds your longest running query, otherwise you might terminate a connection while it is executing a query. |
...