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

["Andrew Polack (JIRA)" <ji...@apache.org>]

Andrew Polack created CURATOR-520:
-------------------------------------

             Summary: NoSuchMethod Exception on curator.close() in 3.4 compatibility mode
                 Key: CURATOR-520
                 URL: https://issues.apache.org/jira/browse/CURATOR-520
             Project: Apache Curator
          Issue Type: Bug
          Components: Client
    Affects Versions: 4.2.0
            Reporter: Andrew Polack
             Fix For: awaiting-response


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: 
{code:java}
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)

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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)