This content has been marked as final. Show 3 replies
Hi, yes, there is a property you can give the driver to make all socket read calls with a timeout.
oracle.net.READ_TIMEOUT. The units are in milliseconds, so choose some number high
enough that no legitimate read, such as a wait for the DBMS to do an update or commit,
etc, would take longer.
Ignore the post by Mukesh. There is nothing relevant there.
My investigations were heading in this direction (e.g., http://docs.oracle.com/cd/B28359_01/java.111/b31224/apxtblsh.htm#CHDBBDDA). However, for WebLogic, is it as simple as adding the following property in the Datasource Connection properties edit box in the WebLogic console?
or do I have to edit the connection URL?
I've tried this, and the Datasource restarts OK after the change, but I have no way right now to check whether it actually "works".
(we have some long-running queries; five minutes seems to be a "safe" limita for now)
Yes, adding it to the properties list and undeploying/redeploying the datasource should do it.