[JAVA-376] ReplicaSetStatus thread still seems alive after Mongo.close() call Created: 10/Jun/11  Updated: 10/Mar/12  Resolved: 10/Mar/12

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: 2.6.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Check to see if the thread is stopped when mongo is closed. The reported error happens after a node fails and returns, and then close() is called.



 Comments   
Comment by Jeffrey Yemin [ 10/Mar/12 ]

Duplicates JAVA-400

Comment by Konrad Kubacki [ 16/Nov/11 ]

Hey, it's easy to reproduce by stoping mongod on server

for example replica set on hosts: mongo01, mongo02, mongo03

then on one of them
user@mongo01 # /etc/init.d/mongodb stop

and then
user@mongo01 # /etc/init.d/mongodb start

The app will put log messages as bellow, till the end of running:

Nov 16, 2011 2:47:52 PM com.mongodb.ReplicaSetStatus$Node update
WARNING: Server seen down: mongo01:27017

checked with driver 2.7.2

Comment by Antoine Girbal [ 19/Jul/11 ]

there is a flag _closed that gets set to true, and thread should stop.
Maybe the node became totally unreachable and the loop was stuck in isMaster.
But there is a 20s timeout anyway..
Not sure this is a bug, is there link to problem?

Generated at Thu Feb 08 08:52:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.