java.util.concurrent.locks

Class AbstractOwnableSynchronizer

Contents
  • All Implemented Interfaces:
    Serializable
    Direct Known Subclasses:
    AbstractQueuedLongSynchronizer, AbstractQueuedSynchronizer

    public abstract class AbstractOwnableSynchronizer
extends Object
implements Serializable
    A synchronizer that may be exclusively owned by a thread. This class provides a basis for creating locks and related synchronizers that may entail a notion of ownership. The AbstractOwnableSynchronizer class itself does not manage or use this information. However, subclasses and tools may use appropriately maintained values to help control and monitor access and provide diagnostics.
    Since:
    1.6
    See Also:
    Serialized Form

    • Constructor Detail

      • AbstractOwnableSynchronizer

        protected AbstractOwnableSynchronizer()
        Empty constructor for use by subclasses.

    • Method Detail

      • setExclusiveOwnerThread

        protected final void setExclusiveOwnerThread(Thread t)
        Sets the thread that currently owns exclusive access. A null argument indicates that no thread owns access. This method does not otherwise impose any synchronization or volatile field accesses.

      • getExclusiveOwnerThread

        protected final Thread getExclusiveOwnerThread()
        Returns the thread last set by setExclusiveOwnerThread, or null if never set. This method does not otherwise impose any synchronization or volatile field accesses.
        Returns:
        the owner thread

Document created the 11/06/2005, last modified the 04/03/2020
Source of the printed document:https://www.gaudry.be/en/java-api-rf-java/util/concurrent/locks/abstractownablesynchronizer.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:fr Manuel PHP : https://docs.oracle.com

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut