[ https://issues.jboss.org/browse/TEIID-1573?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1573: ------------------------------------- I like this approach, than single server wide property. This way it is controlled per connection/session which is desirable. If it is server side, then we have to at a minimum scope it down to a VDB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1573?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1573. ----------------------------------- Resolution: Done Added the ability to set a default query timeout at the vdb level. This can be done through adding a vdb property in the vdb.xml (see the reference vdb chapter). And added the ability to set a server-wide default (see the teiid-jboss-beans.xml). Logically the smallest positive timeout value is the one that will be enforced. JDBC timeouts are still handled on the client side and thus would need to be smaller than either the vdb or server setting to be effective. The notion of server query time starts when the engine receives the query and is in effect until the first result is sent. This will be slightly skewed from the clients query start and first result depending upon network latency. It is possible, but did not seem necessary, to change the notion of server query time to start when the query is first executed. This would mean that anytime spent in queue while waiting for an active plan lease would not be counted against the timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1573?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1573. --------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira