Daniel Kuppitz created TINKERPOP-1184: -----------------------------------------
Summary: Sessions not being closed properly Key: TINKERPOP-1184 URL: https://issues.apache.org/jira/browse/TINKERPOP-1184 Project: TinkerPop Issue Type: Bug Components: server Affects Versions: 3.1.1-incubating Reporter: Daniel Kuppitz Assignee: stephen mallette Currently I see a lot of these messages popping up in the server log: {code} INFO 00:08:33,402 - Session a70d0aeb-92e2-4ff7-88cf-14108e7533d3 has been idle for more than 28800000 milliseconds - preparing to close INFO 00:08:33,402 - Session a70d0aeb-92e2-4ff7-88cf-14108e7533d3 closed {code} I started a bulk loading job more than 8 hours ago, so it seems that it's now closing all the sessions that I ever created. Hoever, I'm confident that I'm closing sessions properly in my code: {code} try { // commit transaction } catch (Exception ex) { // handle exception } finally { client.close(); client = null; } {code} Even if the {{client.close()}} call would fail, I should also see different messages about leaked client connections in the log, but that's not the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)