前言
本文是对Java中Object类的一些方法进行大致介绍，是对于下列文章（文档）的一些概述(持续更新！！！)
参考：java开发帮助文档
以下是本篇文章正文内容，下面案例可供参考
一、Object类基本概述
在Java中，Object类是一个非常重要的类，它是Java中“单根结构”特点的重要体现；从API帮助文档中可以了解到类Objecct是类层次结构的根。当一个类如果没有明确的显示继承一个类（可以理解为该类名后面没有跟上extends关键字，参考代码1.1），则该类默认以Object作为超类（父类或基类）。所有对象（包括数组）都实现此类的方法。
API里关于Object的解释：
Class Object is the root of the class hierarchy. Every class has Object as a superclass. All objects, including arrays, implement the methods of this class.
代码1.1：
class Father{//默认继承Object
}
class Son extends Father{//Java只支持单继承，但其实这个类继承了Father类，而Father继承了Object，因而Son也间接的继承了Object类
}
构造方法
Object类的构造方法只有一个默认的无参构造
//注解
@Target({ElementType.METHOD, ElementType.CONSTRUCTOR})
@Retention(RetentionPolicy.RUNTIME)
public @interface HotSpotIntrinsicCandidate {
}
//Object类的构造方法
/**
* Constructs a new object.
*/
@HotSpotIntrinsicCandidate
public Object() {}
二、Object类中的方法介绍
1、clone方法
@HotSpotIntrinsicCandidate
protected native Object clone() throws CloneNotSupportedException;
这是一个native修饰的方法，用于创建并返回该对象的副本，在JDK中，对clone方法的解释：
- 克隆对象和原来的对象不是同一对象；
- 克隆的类型和原来的类型相等，但不是绝对的要求；
- 克隆的对象和原来的对象进行equals比较是相等，但不是绝对的要求。
- 返回的对象应该通过调用super.clone获得。如果一个类和它的所有父类（Object除外）都遵守这个约定，那么该对象的克隆类型与原来对象的类型相同。
- clone方法返回的对象应独立于此对象（指正在被克隆的对象）。为了实现这种独立性，可能需要在返回对象之前修改super.clone返回的对象的一个或多个字段。通常，这意味着复制构成要克隆对象的内部“深度结构”的任何可变对象，并用对副本的引用替换对这些对象的引用；
如果一个类仅包含基本字段或对不可变对象的引用，则通常情况是无需修改super.clone返回的对象中的任何字段。 - 类Object的方法clone执行特定的克隆操作。首先，如果此对象的类未实现Cloneable接口，则将引发CloneNotSupportedException。请注意，所有数组都被认为实现了Cloneable接口，并且数组类型T []的clone方法的返回类型为T []，其中T为任何引用或原始类型。否则，此方法将创建此对象的类的新实例，并使用该对象相应字段的内容完全初始化其所有字段，就像通过赋值一样；字段的内容本身不会被克隆。因此，此方法执行此对象的“浅复制”，而不是“深复制”操作。
- Object类本身并不实现Cloneable接口，因此在其类为Object的对象上调用clone方法将导致在运行时引发异常。
- 如果对象的类不支持Cloneable。重写clone方法的子类也可以引发CloneNotSupportedException
示例代码如下:
//银行类
class Bank implements Cloneable {
public String bankName;
public int dailyBusinessHours;
public Staff staff;
/**
* 因为clone方法是protected修饰的，要在其它包中访问就需要重写该方法
*/
@Override
protected Object clone() throws CloneNotSupportedException {
return super.clone();
}
}
//员工类
class Staff {
String name;
int age;
}
/**
* @author ExploreJupiter
*/
public class CloneTest{
public static void main(String[] args) throws CloneNotSupportedException {
/**
* 创建对象并初始化
*/
Staff staff = new Staff();
staff.age = 20;
staff.name = "张三";
Bank bank = new Bank();
bank.bankName = "有钱银行";
bank.dailyBusinessHours = 10;
bank.staff = staff;
//验证：克隆对象和原来的对象不是同一对象
//从一下代码中我们也可以看出，两对象的hashcode不一样
Bank bankClone = (Bank) bank.clone();
System.out.println( "原对象:" + bank + ",克隆对象:"+bankClone);
//克隆的类型和原来的类型相等，但不是绝对的要求;
// 从下面的结果可以看出原对象和克隆的对象的类型相同，从clone的定义中，我们可以知道这不是绝对的要求，
// 也就是说克隆对象的类型和原对象的类型可以不相同，我认为应该是一个多态的效果
System.out.println("原对象:" + bank.getClass() + ",克隆对象:" + bankClone.getClass());
//克隆的对象和原来的对象进行equals比较是相等，但不是绝对的要求
//如果我们重写equals方法，让equals方法比较两个对象的属性，那么equals方法比较的结果就是相等的
System.out.println(bank.equals(bankClone));
/*
* clone方法返回的对象应独立于此对象（指正在被克隆的对象）。为了实现这种独立性，
* 可能需要在返回对象之前修改super.clone返回的对象的一个或多个字段。
* 通常，这意味着复制构成要克隆对象的内部“深度结构”的任何可变对象，
* 并用对副本的引用替换对这些对象的引用；
* 如果一个类仅包含基本字段或对不可变对象的引用，
* 则通常情况是无需修改super.clone返回的对象中的任何字段。
* 从以下代码中我们可以发现clone对象和原来的对象的引用是相同的，
* 也就是说，对于可变的引用字段，克隆的是一个引用；当字段是基本数据类型或不可变的引用，不受影响
*/
bankClone.staff.name = "李四";
bankClone.bankName = "快乐银行";
System.out.println(bank.bankName + " " + bankClone.bankName);
System.out.println(bank.staff.name);
System.out.println("原对象：" + bank.staff + "克隆对象：" + bankClone.staff);
}
}
API里关于clone方法的解释：
Creates and returns a copy of this object. The precise meaning of “copy” may depend on the class of the object. The general intent is that, for any object x, the expression:
x.clone() != x
will be true, and that the expression:
x.clone().getClass() == x.getClass()
will be true, but these are not absolute requirements. While it is typically the case that:
x.clone().equals(x)
will be true, this is not an absolute requirement.
By convention, the returned object should be obtained by calling super.clone. If a class and all of its superclasses (except Object) obey this convention, it will be the case that x.clone().getClass() == x.getClass().
By convention, the object returned by this method should be independent of this object (which is being cloned). To achieve this independence, it may be necessary to modify one or more fields of the object returned by super.clone before returning it. Typically, this means copying any mutable objects that comprise the internal “deep structure” of the object being cloned and replacing the references to these objects with references to the copies. If a class contains only primitive fields or references to immutable objects, then it is usually the case that no fields in the object returned by super.clone need to be modified.
The method clone for class Object performs a specific cloning operation. First, if the class of this object does not implement the interface Cloneable, then a CloneNotSupportedException is thrown. Note that all arrays are considered to implement the interface Cloneable and that the return type of the clone method of an array type T[] is T[] where T is any reference or primitive type. Otherwise, this method creates a new instance of the class of this object and initializes all its fields with exactly the contents of the corresponding fields of this object, as if by assignment; the contents of the fields are not themselves cloned. Thus, this method performs a “shallow copy” of this object, not a “deep copy” operation.
The class Object does not itself implement the interface Cloneable, so calling the clone method on an object whose class is Object will result in throwing an exception at run time.
if the object’s class does not support the Cloneable interface. Subclasses that override the clone method can also throw this exception to indicate that an instance cannot be cloned.
clone的好处在于，不用new对象（无论是通过反射还是普通new对象对其实需要new对象），然后将属性的值赋给新的对象，并且该方法是native修饰的，效率更高。
1.1、深拷贝和浅拷贝
深拷贝与浅拷贝的区别就在于，浅拷贝中克隆对象的成员引用指向原来对象成员的引用；深拷贝则是将克隆对象的成员引用也完全的克隆了一份；也就是说深克隆克隆对象和原来的对象是完全分开的，而浅克隆的克隆对象和原来的对象还存在联系。
/* 类Object的方法clone执行特定的克隆操作。
* 首先，如果此对象的类未实现Cloneable接口，则将引发CloneNotSupportedException。
* 请注意，所有数组都被认为实现了Cloneable接口，并且数组类型T []的clone方法的返回类型为T []，
* 其中T为任何引用或原始类型。否则，此方法将创建此对象的类的新实例，
* 并使用该对象相应字段的内容完全初始化其所有字段，就像通过赋值一样；字段的内容本身不会被克隆。
* 因此，此方法执行此对象的“浅复制”，而不是“深复制”操作。
*/
/**
* @author ExploreJupiter
*/
public class ArrayCloneTest{
int[] array = new int[2];
public static void main(String[] args) {
ArrayCloneTest arrayCloneTest = new ArrayCloneTest();
//默认实现Cloneable接口
arrayCloneTest.array.clone();
}
}
1.1.1 实现深克隆的第一种方式
实现原理就是将克隆对象中的可变引用存到一个新的空间中。
class Father implements Cloneable{
int age;
String name;
Son son;
@Override
public Object clone() throws CloneNotSupportedException {
Father clone = (Father) super.clone();
clone.son = (Son) son.clone();
return clone;
}
}
class Son implements Cloneable{
int sAge;
String sName;
@Override
public Object clone() throws CloneNotSupportedException {
return super.clone();
}
}
/**
* @author ExploreJupiter
*/
public class DeepCloning {
public static void main(String[] args) throws CloneNotSupportedException {
Father father = new Father();
father.age = 38;
father.name = "张三";
Son son = new Son();
son.sName ="张思";
son.sAge = 12;
father.son = son;
Father clone1 = (Father) father.clone();
father.son.sName = "张四";
System.out.println(""+father.son.sName + " " + clone1.son.sName);
}
}
1.1.2 实现深克隆的第二种方式
通过序列化的方式实现深克隆，代码之后补充
2、hashCode方法
public native int hashCode();
-
用来返回对象的hash值，支持此方法是为了提高哈希表的性能。
-
如果在Java应用程序的执行过程中对同一对象多次调用hashCode方法，那么hashCode方法必须始终返回相同的整数，前提是没有修改对象的equals比较中使用的信息。此整数对于另一个应用程序的执行所产生的整数不需要保持一致。
-
如果两个对象按照Object类的equals方法进行比较结果相同，则这两个对象调用hashcode方法产生的结果也是相同的
示例代码如下:
/**
* @author ExploreJupiter
*/
public class CloneTest03 {
public static void main(String[] args) {
CloneTest03 cloneTest03 = new CloneTest03();
Object s1 = cloneTest03.hashCode();
Object s2 = cloneTest03.hashCode();
Object s3 = cloneTest03.hashCode();
System.out.println(s1 +" " + s2 +" " + s3 );
}
}
- 如果两个对象按照(java.lang.Object)equals方法结果不相等，那么对这两个对象调用hashCode方法必须生成不同的整数结果。然而，程序员应该知道，为不相等的对象生成不同的整数结果可以提高哈希表的性能。
那这是为什么呢？
这就和哈希表的结构有关了，哈希表是一种数组加链表的形式，先扫描数组，通过数组的hash值，继而找该位置下对应的链表，而不同的对象生成的不同的hash值，也便于寻找元素，提高了查找效率。
API里关于hashCode方法的解释：
Returns a hash code value for the object. This method is supported for the benefit of hash tables such as those provided by HashMap.
The general contract of hashCode is:
Whenever it is invoked on the same object more than once during an execution of a Java application, the hashCode method must consistently return the same integer, provided no information used in equals comparisons on the object is modified. This integer need not remain consistent from one execution of an application to another execution of the same application.
If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result.
It is not required that if two objects are unequal according to the equals(java.lang.Object) method, then calling the hashCode method on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hash tables.
Implementation Requirements:
As far as is reasonably practical, the hashCode method defined by class Object returns distinct integers for distinct objects.
Returns:
a hash code value for this object.
3、equals方法
public boolean equals(Object obj) { //obj表示要与之比较的引用对象
return (this == obj);
}
equals方法，十分的常用，用来判断某个其他对象是否“等于”此对象。
equals方法在非null对象引用上实现等价关系：
- 具有镜像性：对于任何非空的引用值x，x.equals（x）应该返回true。
- 对称性：对于任何非空的引用值x和y，当且仅当y.equals（x）返回true时，x.equals（y）应该返回true。
- 可传递性：对于任何非空的引用值x、y和z，如果x.equals（y）返回true，y.equals（z）返回true，那么x.equals（z）应该返回true。类似于数学中的a=b,b=c,那么a=c;
- 一致性：对于任何非空的引用值x和y，只要不修改对象的equals比较中使用的信息，x.equals（y）的多次调用都会始终返回true或一致返回false。
- 对于任何非空的引用值x，x.equals（null）应返回false。
总的来说，Object类的的equals方法对于任何非空的引用值x和y，当且仅当x和y引用同一对象时（x==y的值为true），此方法才返回true。
注意，每当重写此方法时，通常需要重写hashcode方法，以便维护hashcode方法的常规协定，该协定指出相等的对象必须具有相等的哈希值。
API里关于equals方法的解释：
ndicates whether some other object is “equal to” this one.
The equals method implements an equivalence relation on non-null object references:
It is reflexive: for any non-null reference value x, x.equals(x) should return true.
It is symmetric: for any non-null reference values x and y, x.equals(y) should return true if and only if y.equals(x) returns true.
It is transitive: for any non-null reference values x, y, and z, if x.equals(y) returns true and y.equals(z) returns true, then x.equals(z) should return true.
It is consistent: for any non-null reference values x and y, multiple invocations of x.equals(y) consistently return true or consistently return false, provided no information used in equals comparisons on the objects is modified.
For any non-null reference value x, x.equals(null) should return false.
The equals method for class Object implements the most discriminating possible equivalence relation on objects; that is, for any non-null reference values x and y, this method returns true if and only if x and y refer to the same object (x == y has the value true).
Note that it is generally necessary to override the hashCode method whenever this method is overridden, so as to maintain the general contract for the hashCode method, which states that equal objects must have equal hash codes.
Parameters:
obj - the reference object with which to compare.
Returns:
true if this object is the same as the obj argument; false otherwise.
4、toString方法
public String toString() {
//返回结果：该实例对象所对应的类名称@对象哈希代码的无符号十六进制表示形式
return getClass().getName() + "@" + Integer.toHexString(hashCode());
}
toString方法可以说是既陌生又不陌生，相信小伙伴们一定做过一件事就是直接将一个对象的引用放在print语句中，结果是一些看不懂的东西（见代码1.2）当我们比较调用该对象的toString方法，和不调用该对象的toString方法得到的结果是一样的。这也可以得出当我们直接输出一个对象时，其默认调用该对象的toString方法。
代码1.2：
/**
*java中的toStrong方法
* @author ExploreJupiter
*/
public class ToStringTest {
public static void main(String[] args) {
ToStringTest toStringTest = new ToStringTest();
System.out.println(toStringTest);
System.out.println(toStringTest.toString());
}
}
运行结果：
com.chengqi.javase.review.ToStringTest@10f87f48
com.chengqi.javase.review.ToStringTest@10f87f48
Process finished with exit code 0
toSting方法的作用就是将一个对象，以字符串的形式表示，在文档中也说明了，toString方法返回的结果应该是一个简洁，但翔实的表述，便于阅读的，并且建议所有子类都重写此方法。
API里关于toString方法的解释：
Returns a string representation of the object. In general, the toString method returns a string that “textually represents” this object. The result should be a concise but informative representation that is easy for a person to read. It is recommended that all subclasses override this method.
The toString method for class Object returns a string consisting of the name of the class of which the object is an instance, the at-sign character `@’, and the unsigned hexadecimal representation of the hash code of the object. In other words, this method returns a string equal to the value of:
getClass().getName() + ‘@’ + Integer.toHexString(hashCode())
5、finalize方法
@Deprecated(since="9")
protected void finalize() throws Throwable { }
当垃圾回收确定不再有对象的引用时，由对象上的垃圾回收器调用。子类重写finalize方法以释放系统资源或执行其他清理。
-
finalize() 方法是在垃圾收集器删除对象之前被自动调用的，只需要在自己的类中重写，不需要自己调用，但是JVM并不会保证该方法总是调用。
-
这是一个已经过时的方法，该方法可能导致性能问题、死锁和挂起；文档中也提到了Cleaner和PhantomReference在对象变得不可访问时提供了更灵活、更高效的释放资源的方法。
如果子类重写finalize，它必须显式调用父类的finalize方法。为了防止异常过早终止finalize链，子类应该使用try finally块来确保super.finalize()始终被调用（见代码1.3）。
代码1.3：
@Override
protected void finalize() throws Throwable {
try {
... // cleanup subclass state
} finally {
super.finalize();
}
}
从源码中也可以发现类Object的finalize方法不执行任何特殊操作；它只是正常返回。
finalize方法引发的任何异常都会导致此对象的终结停止，但会被忽略。（未搞懂，暂不做解释）
5.1、对象复活
对象复活代码实现，和更好的解释，本文不做概述
API里关于finalize方法的解释：
Deprecated.
The finalization mechanism is inherently problematic. Finalization can lead to performance issues, deadlocks, and hangs. Errors in finalizers can lead to resource leaks; there is no way to cancel finalization if it is no longer necessary; and no ordering is specified among calls to finalize methods of different objects. Furthermore, there are no guarantees regarding the timing of finalization. The finalize method might be called on a finalizable object only after an indefinite delay, if at all. Classes whose instances hold non-heap resources should provide a method to enable explicit release of those resources, and they should also implement AutoCloseable if appropriate. The Cleaner and PhantomReference provide more flexible and efficient ways to release resources when an object becomes unreachable.
Called by the garbage collector on an object when garbage collection determines that there are no more references to the object. A subclass overrides the finalize method to dispose of system resources or to perform other cleanup.
The general contract of finalize is that it is invoked if and when the Java™ virtual machine has determined that there is no longer any means by which this object can be accessed by any thread that has not yet died, except as a result of an action taken by the finalization of some other object or class which is ready to be finalized. The finalize method may take any action, including making this object available again to other threads; the usual purpose of finalize, however, is to perform cleanup actions before the object is irrevocably discarded. For example, the finalize method for an object that represents an input/output connection might perform explicit I/O transactions to break the connection before the object is permanently discarded.
The finalize method of class Object performs no special action; it simply returns normally. Subclasses of Object may override this definition.
The Java programming language does not guarantee which thread will invoke the finalize method for any given object. It is guaranteed, however, that the thread that invokes finalize will not be holding any user-visible synchronization locks when finalize is invoked. If an uncaught exception is thrown by the finalize method, the exception is ignored and finalization of that object terminates.
After the finalize method has been invoked for an object, no further action is taken until the Java virtual machine has again determined that there is no longer any means by which this object can be accessed by any thread that has not yet died, including possible actions by other objects or classes which are ready to be finalized, at which point the object may be discarded.
The finalize method is never invoked more than once by a Java virtual machine for any given object.
Any exception thrown by the finalize method causes the finalization of this object to be halted, but is otherwise ignored.
API Note:
Classes that embed non-heap resources have many options for cleanup of those resources. The class must ensure that the lifetime of each instance is longer than that of any resource it embeds. Reference.reachabilityFence(java.lang.Object) can be used to ensure that objects remain reachable while resources embedded in the object are in use.
A subclass should avoid overriding the finalize method unless the subclass embeds non-heap resources that must be cleaned up before the instance is collected. Finalizer invocations are not automatically chained, unlike constructors. If a subclass overrides finalize it must invoke the superclass finalizer explicitly. To guard against exceptions prematurely terminating the finalize chain, the subclass should use a try-finally block to ensure super.finalize() is always invoked. For example,
@Override
protected void finalize() throws Throwable {
try {
… // cleanup subclass state
} finally {
super.finalize();
}
}
6、getClass方法
@HotSpotIntrinsicCandidate
public final native Class<?> getClass();
返回此对象的运行时类。
返回的Class对象是被表示的类的静态同步方法锁定的对象。
返回：表示该对象的运行时类的 java.lang.Class 对象。此结果属于类型 Class<? extends X>，其中 X 表示清除表达式中的静态类型，该表达式调用 getClass。
Number n = 0;
Class<? extends Number> c = n.getClass();
API里关于getClass方法的解释：
Returns the runtime class of this Object. The returned Class object is the object that is locked by static synchronized methods of the represented class.
The actual result type is Class<? extends |X|> where |X| is the erasure of the static type of the expression on which getClass is called. For example, no cast is required in this code fragment:
Number n = 0;
Class<? extends Number> c = n.getClass();
Returns:
The Class object that represents the runtime class of this object.
7、notify方法
@HotSpotIntrinsicCandidate
public final native void notify();
唤醒正在该对象的监视器上等待的单个线程，是随机的。
-
如果有线程正在等待此对象，则选择其中一个线程被唤醒。这种选择是任意的，由执行者自行决定。线程通过调用其中一个wait方法等待对象的监视器。
-
在当前线程放弃对该对象的锁定之前，唤醒的线程将无法继续。被唤醒的线程将以正常的方式与任何其他线程竞争，这些线程可能正积极地在该对象上进行同步；此方法只能由作为此对象监视器所有者的线程调用。线程通过以下三种方式之一成为对象监视器的所有者：
1、通过执行该对象的同步实例方法。
2、通过执行在对象上同步的同步语句体。
3、对于CLass类型的对象，通过执行该类的同步静态方法。
-
一次只能有一个线程拥有一个对象的监视器。
API里关于notify方法的解释：
Wakes up a single thread that is waiting on this object’s monitor. If any threads are waiting on this object, one of them is chosen to be awakened. The choice is arbitrary and occurs at the discretion of the implementation. A thread waits on an object’s monitor by calling one of the wait methods.
The awakened thread will not be able to proceed until the current thread relinquishes the lock on this object. The awakened thread will compete in the usual manner with any other threads that might be actively competing to synchronize on this object; for example, the awakened thread enjoys no reliable privilege or disadvantage in being the next thread to lock this object.
This method should only be called by a thread that is the owner of this object’s monitor. A thread becomes the owner of the object’s monitor in one of three ways:
By executing a synchronized instance method of that object.
By executing the body of a synchronized statement that synchronizes on the object.
For objects of type Class, by executing a synchronized static method of that class.
Only one thread at a time can own an object’s monitor.
8、notifyAll方法
@HotSpotIntrinsicCandidate
public final native void notifyAll();
notifyAll方法，唤醒在该对象监视器上等待的所有线程。
- 线程通过调用其中一个wait方法等待对象的监视器。在当前线程放弃此对象的锁之前，唤醒的线程将无法继续。被唤醒的线程将以正常的方式与任何其他线程竞争，这些线程可能正积极地在该对象上进行同步；此方法只能由作为此对象监视器所有者的线程调用。有关线程成为监视器所有者的方式的说明，可以参考notify方法。
9、wait(long timeoutMillis, int nanos)方法
public final void wait(long timeoutMillis, int nanos) throws InterruptedException {
if (timeoutMillis < 0) {
throw new IllegalArgumentException("timeoutMillis value is negative");
}
if (nanos < 0 || nanos > 999999) {
throw new IllegalArgumentException(
"nanosecond timeout value out of range");
}
if (nanos > 0 && timeoutMillis < Long.MAX_VALUE) {
timeoutMillis++;
}
wait(timeoutMillis);
}
使当前线程等待，直到它被唤醒，通常是通过被通知或中断，或者直到经过一定的实时时间。
-
当前线程必须拥有此对象的监视器锁。有关线程成为监视器锁所有者的方式的描述，请参见notify方法。
-
此方法使当前线程（在这里称为T）将自己放入该对象的等待集中，然后放弃对该对象的所有同步声明。请注意，只有此对象上的锁被放弃；当线程等待时，当前线程可能同步的任何其他对象将保持锁定。然后，出于线程调度的目的，线程T被禁用，并处于休眠状态，直到出现以下情况之一：
1.另一个线程调用这个对象的notify方法，而thread T恰好被任意选择为要唤醒的线程。
2.另一个线程为此对象调用notifyAll方法。
3.另一个线程中断线程T。
4.指定的超时时间已过（超时时间表达式：1000000*timeoutMillis+nanos）；如果timeoutMillis和nanos都为零，则不考虑这一情况，线程将等待，直到被上述的其它情况唤醒。 -
建议的等待方法是在while循环中检查等待的条件，该循环围绕着wait调用，如下例所示，这种方法避免了可能由虚假唤醒（线程可以在没有被通知、中断或超时的情况下被唤醒）引起的问题。
synchronized (obj) {
while (<condition does not hold> and <timeout not exceeded>) {
long timeoutMillis = ... ; // recompute timeout values
int nanos = ... ;
obj.wait(timeoutMillis, nanos);
}
... // Perform action appropriate to condition or timeout
}
API里关于wait(long timeoutMillis, int nanos)方法的解释：
Causes the current thread to wait until it is awakened, typically by being notified or interrupted, or until a certain amount of real time has elapsed.
The current thread must own this object’s monitor lock. See the notify method for a description of the ways in which a thread can become the owner of a monitor lock.
This method causes the current thread (referred to here as T) to place itself in the wait set for this object and then to relinquish any and all synchronization claims on this object. Note that only the locks on this object are relinquished; any other objects on which the current thread may be synchronized remain locked while the thread waits.
Thread T then becomes disabled for thread scheduling purposes and lies dormant until one of the following occurs:
Some other thread invokes the notify method for this object and thread T happens to be arbitrarily chosen as the thread to be awakened.
Some other thread invokes the notifyAll method for this object.
Some other thread interrupts thread T.
The specified amount of real time has elapsed, more or less. The amount of real time, in nanoseconds, is given by the expression 1000000 * timeoutMillis + nanos. If timeoutMillis and nanos are both zero, then real time is not taken into consideration and the thread waits until awakened by one of the other causes.
Thread T is awakened spuriously. (See below.)
The thread T is then removed from the wait set for this object and re-enabled for thread scheduling. It competes in the usual manner with other threads for the right to synchronize on the object; once it has regained control of the object, all its synchronization claims on the object are restored to the status quo ante - that is, to the situation as of the time that the wait method was invoked. Thread T then returns from the invocation of the wait method. Thus, on return from the wait method, the synchronization state of the object and of thread T is exactly as it was when the wait method was invoked.
A thread can wake up without being notified, interrupted, or timing out, a so-called spurious wakeup. While this will rarely occur in practice, applications must guard against it by testing for the condition that should have caused the thread to be awakened, and continuing to wait if the condition is not satisfied. See the example below.
For more information on this topic, see section 14.2, “Condition Queues,” in Brian Goetz and others’ Java Concurrency in Practice (Addison-Wesley, 2006) or Item 69 in Joshua Bloch’s Effective Java, Second Edition (Addison-Wesley, 2008).
If the current thread is interrupted by any thread before or while it is waiting, then an InterruptedException is thrown. The interrupted status of the current thread is cleared when this exception is thrown. This exception is not thrown until the lock status of this object has been restored as described above.
API Note:
The recommended approach to waiting is to check the condition being awaited in a while loop around the call to wait, as shown in the example below. Among other things, this approach avoids problems that can be caused by spurious wakeups.
synchronized (obj) {
while ( and ) {
long timeoutMillis = … ; // recompute timeout values
int nanos = … ;
obj.wait(timeoutMillis, nanos);
}
… // Perform action appropriate to condition or timeout
}
Parameters:
timeoutMillis - the maximum time to wait, in milliseconds
nanos - additional time, in nanoseconds, in the range 0-999999 inclusive
10、wait()方法
public final void wait() throws InterruptedException {
wait(0L);
}
使当前线程等待，直到它被唤醒，通常是通过被通知或中断。
有关详细信息，请参阅wait（long，int）方法的规范。
通过源码可以发现，其内部其实是调用的wait（）方法，该long类型的值为0L;
11、wait(long timeoutMillis)方法
public final native void wait(long timeoutMillis) throws InterruptedException;
使当前线程等待，直到它被唤醒，通常是通过被通知或中断，或者直到经过一定的实时时间。
有关详细信息，请参阅wait（long，int）方法的规范。
总结
这里对文章进行总结：
本文主要是对API中Object的一些介绍进行，浅层次的分析，再扩展了一些内容，可能存在一些错误，望各位可以指正，不胜感激！！！
604
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
