[CURATOR-520] NoSuchMethod Exception on curator.close() in 3.4 compatibility mode

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 4.2.0
• Fix Version/s: 4.2.0
• Component/s: Client
• Assignee: Unassigned
• Reporter: Andrew Polack
• Created: 21/May/19 12:46
• Updated: 21/May/19 20:48
• Resolved: 21/May/19 20:35

Description

Running in 3.4 compatibility mode, Curator improperly appears to attempt to call the close(I) method which does not exist on the 3.4 version of the Zookeeper API: 

Uncaught error from thread [timeline-manager-akka.actor.default-dispatcher-4]: org.apache.zookeeper.ZooKeeper.close(I)Z, shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[timeline-manager]
java.lang.NoSuchMethodError: org.apache.zookeeper.ZooKeeper.close(I)Z
at org.apache.curator.HandleHolder.internalClose(HandleHolder.java:164)
at org.apache.curator.HandleHolder.closeAndClear(HandleHolder.java:78)
at org.apache.curator.ConnectionState.close(ConnectionState.java:125)
at org.apache.curator.CuratorZookeeperClient.close(CuratorZookeeperClient.java:266)
at org.apache.curator.CuratorZookeeperClient.close(CuratorZookeeperClient.java:249)

This results in a failure to reconnect to Zookeeper when the service is restarted (presumably because the old connection was never properly released).