Does .close() need to be called after every gremlin query?

[Daniel Craig]

Hi all, in our apps we have a long-lived graph traversal source that never gets .close() called on it - this has never caused an issue before, but after an upgrade we are seeing error messages like the following: ""Remote connection to [/10.161.113.6:35548] failed with javax.net .ssl.SSLException: Cannot kickstart, the connection is broken or closed""  Is this likely to be resolved by calling .close() after each traversal?

[Kelvin Lawrence]

Hi Daniel,

You should not need to call close after each traversal. In general the recommended approach is to re-use the existing connection as much as possible and not close it. Which client version are you using? Is that backend a Gremlin Server in this case?

Cheers,

Kelvin

[Daniel Craig]

I am encountering this error and I'm having a bit of trouble narrowing down how it occurs, so I appreciate your response.  We are using client version 3.4.11 and the backend is a Neptune db.