SNOW-1846692: Getting a lot of "Failed to close session" Errors After upgrading to 4.2.0

[NivNetzer]

Since upgrading the driver to 4.2.0 we're seeing a lot of "Failed to close session"
We don't believe this is a new error but a product of this commit Raising the response error log level from debug to error.

If the definition has now changed from debug to error, what action should we take?

Here's an example of an error
Failed to close session: 846189017238125, error ignored. Code: 390112 Message: Your session has expired. Please login again.

[sfc-gh-dszmolka]

hi - this sounds the expected behaviour to me. Sessions by default are valid for 4 hours, afterwards for any subsequent query issued in the same session, user needs to authenticate again. Note the word 'any' here - it's also valid for the call to close the session.

You can either ignore these errors for session close, or check if the session is still valid (e.g. try to submit a query) and only try to close them if they're still valid.

Or use our connection pooling and let the pool manager manage the underlying connections. There's extensive documentation for it. Hope this helps.