Skip to main content
  • EN

Hi, I have a few sql executor transformers in a sequence. They are using sql server jdbc driver connections. When I run I get the following notices usually from either the second or the third executor in the chain.

com.microsoft.sqlserver.jdbc.SQLServerException: The query has timed out.

 

I have in the past got round this by putting in feature holders which seem to close the existing connection session but it doesnt appear to be working and is affecting workbenches in desktop and cloud. I dont get these issues with using the native sql client but because I need them to run in cloud they need to be on jdbc.

 

Does anyone have any suggestions as to work arounds for this. thank you

The FeatureHolders would normally have no impact on query timeouts.

Have you tried increasing the timeout in the SQLExecutor connection parameters?

sqlserver_timeoutThat works for me.

The FeatureHolders would normally have no impact on query timeouts.

Have you tried increasing the timeout in the SQLExecutor connection parameters?

sqlserver_timeoutThat works for me.

thanks david_r, seems like when I upgraded to the latest jdbc driver this reset back to 30, hopefully that will sort it. Thank you

Reply


Community Stats

30,163
Posts
114,500
Replies
37,814
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.