Package org.jruby.internal.runtime
Class ThreadService
ThreadService maintains references to all JRuby-specific thread data structures
needed for Ruby's threading API and for JRuby's execution. The main
structures are:
- ThreadContext, which contains frames, scopes, etc needed for Ruby execution
- RubyThread, the Ruby object representation of a thread's state
- RubyThreadGroup, which represents a group of Ruby threads
- RubyNativeThread, used to wrap threads owned by the current Ruby runtime
- AdoptedNativeThread, used to wrap threads managed outside of JRuby
- ThreadService is itself a ThreadLocal, which holds a soft reference to a ThreadContext. So the thread's locals softly reference ThreadContext. We use a soft reference to keep ThreadContext instances from going away too quickly when a Java thread leaves Ruby space completely, which would otherwise result in a lot of ThreadContext object churn.
- ThreadService maintains a weak map from the actual java.lang.Thread instance to the associated RubyThread. The map is weak-keyyed, so it will not prevent the collection of the associated Thread. The associated RubyThread will remain alive as long as the Thread and this ThreadService instance are both alive, maintaining the external thread's identity in Ruby-land.
- RubyThread has a weak reference to its to ThreadContext.
- ThreadContext has a hard reference to its associated RubyThread. Ignoring other references, this will usually mean RubyThread is softly reachable via the soft threadlocal reference to ThreadContext in ThreadService.
- RubyThreadGroup has hard references to threads it owns. The thread removes itself on termination (if it's a Ruby thread) or when the ThreadContext is collected (as in the case of "adopted" Java threads.
- A Ruby thread is started. This constructs a new RubyThread object, which calls to ThreadService to initialize a ThreadContext and appropriate mappings in all ThreadService's structures. The body of the thread is wrapped with a finally block that will forcibly unregister the thread and all related structures from ThreadService.
- A Java thread enters Ruby by doing a call. The thread is "adopted", and gains a RubyThread instance, a ThreadContext instance, and all associated mappings in ThreadService. Since we don't know when the thread has "left" Ruby permanently, no forcible unregistration is attempted for the various structures and maps. However, they should not be hard-rooted; the ThreadContext is only softly reachable at best if no calls are in-flight, so it will collect. Its collection will release the reference to RubyThread, and its finalizer will unregister that RubyThread from its RubyThreadGroup. With the RubyThread gone, the Thread-to-RubyThread map will eventually clear, releasing the hard reference to the Thread itself.
-
Nested Class Summary
Nested Classes -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoid
associateThread
(Thread thread, RubyThread rubyThread) void
deliverEvent
(RubyThread sender, RubyThread target, ThreadService.Event event) Deprecated.void
Deprecated.void
dissociateThread
(Object thread) Deprecated.boolean
Deprecated.final ThreadContext
In order to provide an appropriate execution context for a given thread, we store ThreadContext instances in a threadlocal.static ThreadContext
getCurrentContext
(ThreadService service) boolean
Deprecated.Deprecated.Deprecated.getThreadContextForThread
(RubyThread thread) Deprecated.long
void
registerNewThread
(RubyThread thread) void
setCritical
(boolean critical) Deprecated.final void
setCurrentContext
(ThreadContext context) Deprecated.void
setMainThread
(Thread thread, RubyThread rubyThread) void
teardown()
void
unregisterCurrentThread
(ThreadContext context) void
unregisterThread
(RubyThread thread) Methods inherited from class java.lang.ThreadLocal
get, initialValue, remove, set, withInitial
-
Constructor Details
-
ThreadService
-
-
Method Details
-
teardown
public void teardown() -
initMainThread
public void initMainThread() -
getCurrentContext
In order to provide an appropriate execution context for a given thread, we store ThreadContext instances in a threadlocal. This method is a utility to get at that threadlocal context from anywhere in the program it may not be immediately available. This method should be used sparingly, and if it is possible to pass ThreadContext on the argument list, it is preferable. Description of behavior The threadlocal does not actually contain the ThreadContext directly; instead, it contains a SoftReference that holds the ThreadContext. This is to allow new threads to enter the system and execute Ruby code with a valid context, but still allow that context to garbage collect if the thread stays alive much longer. We use SoftReference here because WeakReference is collected too quickly, resulting in very expensive ThreadContext churn (and this originally lead to JRUBY-2261's leak of adopted RubyThread instances).- Returns:
- The ThreadContext instance for the current thread, or a new one if none has previously been created or the old ThreadContext has been collected.
-
getCurrentContext
-
registerNewThread
-
getMainThread
-
setMainThread
-
getActiveRubyThreads
-
associateThread
-
unregisterThread
-
unregisterCurrentThread
-
disposeCurrentThread
Deprecated. -
incrementAndGetThreadCount
public long incrementAndGetThreadCount() -
getRubyThreadMap
Deprecated. -
deliverEvent
@Deprecated public void deliverEvent(RubyThread sender, RubyThread target, ThreadService.Event event) Deprecated. -
getRubyThreadGroup
Deprecated. -
getThreadContextForThread
Deprecated. -
dissociateThread
Deprecated. -
setCurrentContext
Deprecated. -
getPolling
Deprecated. -
setCritical
Deprecated. -
getCritical
Deprecated.
-