jTDS Driver Questions

[Monster]

We have been experiencing some Socket.Read() errors causing the thread to never terminate, thus resulting in thread depletion.

We are currently using the JDBC with default connectionTimeout set (1 minute).

We have read that switching to the jTDS driver is a good idea, and using the socketTimeout to kill threads that have no activity.

Railo specific questions:

1. What exactly does the datasource "Connection Timeout" do in the jTDS driver settings? It appears to be the timeout setting for establishing a connection (loginTimeout for jTDS), but the documentation isn't specific.

2. In the Railo Admin it says that the Connection Timeout units are "(in minutes)", yet when you save the datasource and get the json string for your config files the comments say that the units are in seconds. Seconds would match the jTDS loginTimeout units. Which is it?

",connectionTimeout:9 // default: 1; unit: seconds"

3. Because socketTimeout is not an option via the Railo Server Admin, we are experimenting with passing the socketTimeout as part of the connection string like so:

'_database' :
{
'class': 'net.sourceforge.jtds.jdbc.Driver'
, 'connectionString': 'jdbc:jtds:sqlserver://<host>:1433;DatabaseName=<db_name>;sendStringParametersAsUnicode=true;SelectMethod=direct;socketTimeout=120'
, 'username': '<username>'
, 'password': "encrypted:<password>"
},

Anyone have any experience with using socketTimeout and jTDS?

Thanks,
m