Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.1.3
-
None
-
None
Description
Namely, the ioPool and coreScheduler should be cleaned up properly IFF the environment created them. If the user provided them, then they may be reused elsewhere and it is the responsibility of the user to shutdown them properly.
Provide a shutdown hook and implement it for internally-created resources, have the user provide it otherwise.
Attachments
Issue Links
- relates to
-
JCBC-773 The v2 of the java client leaks RxJava threads on shutdown
- Resolved
For Gerrit Dashboard: JVMCBC-201 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
51363,3 | JVMCBC-201: shutdown coreScheduler properly | master | couchbase-jvm-core | Status: MERGED | +2 | +1 |
51366,2 | take JVMCBC-201 overloads of ioPool/scheduler into account | master | couchbase-java-client | Status: MERGED | +2 | +1 |
51561,1 | JVMCBC-201: shutdown coreScheduler properly | master | couchbase-jvm-core | Status: ABANDONED | 0 | 0 |
51562,2 | JVMCBC-201: shutdown coreScheduler properly | release11 | couchbase-jvm-core | Status: MERGED | +2 | +1 |
51563,2 | take JVMCBC-201 overloads of ioPool/scheduler into account | release21 | couchbase-java-client | Status: MERGED | +2 | +1 |
52225,2 | JVMCBC-201: Ignore IO pool errors on shutdown. | release11 | couchbase-jvm-core | Status: MERGED | +2 | +1 |
52226,2 | JVMCBC-201: Ignore IO pool errors on shutdown. | master | couchbase-jvm-core | Status: MERGED | +2 | +1 |