[ZOOKEEPER-795] eventThread isn't shutdown after a connection "session expired" event coming

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.3.1
• Fix Version/s: 3.3.2, 3.4.0
• Component/s: java client

Environment

ubuntu 10.04

• Assignee: Sergey Doroshenko
• Reporter: mathieu barcikowski
• Created: 28/Jun/10 10:12
• Updated: 13/Jun/13 18:28
• Resolved: 17/Aug/10 20:05

Description

Hi,

I notice a problem with the eventThread located in ClientCnxn.java file.
The eventThread isn't shutdown after a connection "session expired" event coming (i.e. never receive EventOfDeath).

When a session timeout occurs and the session is marked as expired, the connexion is fully closed (socket, SendThread...) expect for the eventThread.
As a result, if i create a new zookeeper object and connect through it, I got a zombi thread which will never be kill (as for the previous zookeeper object, the state is already close, calling close again don't do anything).

So everytime I will create a new zookeeper connection after a expired session, I will have a one more zombi EventThread.

How to reproduce :

• Start a zookeeper client connection in debug mode
• Pause the jvm enough time to the expired event occur
• Watch for example with jvisualvm the list of threads, the sendThread is succesfully killed, but the EventThread go to wait state for a infinity of time
• if you reopen a new zookeeper connection, and do again the previous steps, another EventThread will be present in infinite wait state

Issue Links

• is related to: DOSGI-191 ZooKeeperDiscovery instance reconnects to ZooKeeper after bundle is stopped