Project

General

Profile

Actions
Copy link

Bug #12342

closed
Actions
Copy link
#2 [ruby-core:75386]

Updated by jrafanie (Joe Rafaniello) about 9 years ago

I have opened a pull request to expose an API for killing the timer thread. This PR should be enough to workaround this issue for me, although it would be nice if DRb.start_service could be responsible for creating/starting the timer and stop_service could then automatically stop any timer thread created by the service:

https://.com/ruby/ruby/pull/1342

Actions
Copy link
#3

Updated by seki (Masatoshi Seki) about 9 years ago

  • Status changed from Open to Closed

Applied in changeset r55008.

don't use keeper thread. [Bug ]

Actions
Copy link
#4 [ruby-core:75885]

Updated by usa (Usaku NAKAMURA) about 9 years ago

  • Backport changed from 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN to 2.1: WONTFIX, 2.2: REQUIRED, 2.3: REQUIRED
Actions
Copy link
#5 [ruby-core:76840]

Updated by nagachika (Tomoyuki Chikanaga) almost 9 years ago

  • Backport changed from 2.1: WONTFIX, 2.2: REQUIRED, 2.3: REQUIRED to 2.1: WONTFIX, 2.2: REQUIRED, 2.3: DONE

ruby_2_3 r55867 merged revision(s) 55008.

Actions
Copy link
#6 [ruby-core:76916]

Updated by usa (Usaku NAKAMURA) almost 9 years ago

  • Backport changed from 2.1: WONTFIX, 2.2: REQUIRED, 2.3: DONE to 2.1: WONTFIX, 2.2: DONE, 2.3: DONE

ruby_2_2 r55929 merged revision(s) 55008.

Actions
Copy link

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0