 |
 |
Archives of the TeradataForum
Message Posted: Mon, 02 May 2005 @ 14:41:48 GMT
Subj: | | Re: JDBC Exception need help!!! |
|
From: | | Kallarakkal, Baburaj (B.) |
You can get aroudn with this by using the REFRESH interval option of your connection pool, which means the sessions always sends a query in to
refresh the connection making the idle time only to a set interval 30mts/1 hour etc. Your Teradata Manager might have a setting to have the IDLE
sessions aborted after a definite time interval and your REFRESH period should be within this interval, so the IDLE time never reaches this
threshold.
Regards,
Raj
| |