Skip to main content
Solved

sql server jdbc timeout issues

  • January 27, 2021
  • 2 replies
  • 242 views
oliver.morris
Contributor
Forum|alt.badge.img+14

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

Best answer by david_r

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.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

david_r
Celebrity
  • david_rCelebrity
  • Best Answer
  • January 27, 2021

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.

oliver.morris
Contributor
Forum|alt.badge.img+14
  • oliver.morrisContributor
  • Author
  • Contributor
  • January 27, 2021

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

Community Stats

32,154
Posts
122,047
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.