[TINKERPOP-1172] Reconnect to Gremlin Server previously marked as dead

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.1-incubating
• Fix Version/s: 3.2.0-incubating, 3.1.2-incubating
• Component/s: driver
• Assignee: Stephen Mallette
• Reporter: Stephen Mallette
• Created: 19/Feb/16 19:19
• Updated: 25/Feb/16 14:51
• Resolved: 25/Feb/16 14:51

Description

We have a test to validate that this works when connecting to multiple servers in a round-robin fashion but nothing that tests against a single server and it seems that there are some problems around that particular situation. It tends to manifest as:

Caused by: java.lang.NullPointerException: null
	at org.apache.tinkerpop.gremlin.driver.ConnectionPool.considerUnavailable(ConnectionPool.java:392) ~[gremlin-driver-3.1.2-SNAPSHOT.jar:3.1.2-SNAPSHOT]
	at org.apache.tinkerpop.gremlin.driver.ConnectionPool.<init>(ConnectionPool.java:101) ~[gremlin-driver-3.1.2-SNAPSHOT.jar:3.1.2-SNAPSHOT]
	at org.apache.tinkerpop.gremlin.driver.Client$SessionedClient.initializeImplementation(Client.java:558) ~[gremlin-driver-3.1.2-SNAPSHOT.jar:3.1.2-SNAPSHOT]
	at org.apache.tinkerpop.gremlin.driver.Client.init(Client.java:117) ~[gremlin-driver-3.1.2-SNAPSHOT.jar:3.1.2-SNAPSHOT]
	at org.apache.tinkerpop.gremlin.driver.Client.submitAsync(Client.java:182) ~[gremlin-driver-3.1.2-SNAPSHOT.jar:3.1.2-SNAPSHOT]
	at org.apache.tinkerpop.gremlin.driver.Client.submitAsync(Client.java:174) ~[gremlin-driver-3.1.2-SNAPSHOT.jar:3.1.2-SNAPSHOT]
	at org.apache.tinkerpop.gremlin.driver.Client.submit(Client.java:144) ~[gremlin-driver-3.1.2-SNAPSHOT.jar:3.1.2-SNAPSHOT]
	... 21 common frames omitted

when the ConnectionPool can not be intialized in any way at start up. If that happens the Client doesn't seem to recover well.