java是抢占式线程，一个线程就是进程中单一的顺序控制流，单个进程可以拥有多个并发任务，其底层是切分cpu时间，多线程和多任务往往是使用多处理器系统的最合理方式
进程可以看作一个程序或者一个应用；线程是进程中执行的一个任务，多个线程可以共享资源
一个java 应用从main 方法开始运行，main 运行在一个线程内，也被称为 “主线程”，runnable也可以理解为task (任务)
jvm启动后，会创建一些守护线程来进行自身的常规管理（垃圾回收，终结处理），以及一个运行main函数的主线程
随着硬件水平的提高，多线程能使系统的运行效率得到大幅度的提高，同时异步操作也增加复杂度和各种并发问题
■ 线程 vs 进程
在一个已有进程中创建一个新线程比创建一个新进程快的多
终止一个线程比终止一个进程快的多
同一个进程内线程间切换比进程间切换更快
线程提供了不同的执行程序间通信的效率，同一个进程中的线程共享同一进程内存和文件，无序调用内核就可以互相通信，而进程间通信必须通过内核
■ 同步和异步
同步方法一旦开始，调用者必须等到方法调用返回之后，才能继续后续行为
无先后顺序，一旦开始，方法调用便立即返回，调用者就可以继续后续行为，一般为另一个线程执行
■ 阻塞和非阻塞
当一个线程占用临界区资源，其他线程也想要使用该资源就必须等待，等待会导致线程的挂起，也就是阻塞(线程变成阻塞状态)。
此时若占用资源的线程一直不愿意释放资源，那么其他所有阻塞在该临界区的线程都会被挂起，变成阻塞状态，不能正常工作，直到占用线程释放资源
非阻塞强调没有一个线程可以妨碍其他线程执行，所有线程都会尝试去做下一步工作
■ 临界资源与临界区
一般指的是公共共享资源，即可以被多个线程共享使用。但同一时间只能由一个线程去访问和操作临界区的资源，一旦临界区资源被一个线程占用，其他线程也想要使用该资源就必须等待，
就好比好多人想上大号，但只有一个坑，一个人占了坑，其他人就得排队等待喽
临界区可以认为是一段代码，线程会在该端代码中访问共享资源，因此临界区的界定标准就是是否访问共享(临界)资源（有点类似形成闭包的概念）；一次只允许有一个程序(进程/线程)在该临界区中
■ 类定义
|
1
2
3
4
5
6
7
8
|
public class thread implements runnable { /* make sure registernatives is the first thing <clinit> does. 初始化时调用 java 本地方法，实现了runnable接口 */ private static native void registernatives(); static { registernatives(); } |
■ 构造器
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
|
/** * 默认构造器 * 其中name规则为 "thread-" + nextthreadnum() */public thread() { init(null, null, "thread-" + nextthreadnum(), 0);}/** * 创建一个指定runnable的线程 * 其中name规则为 "thread-" + nextthreadnum() */public thread(runnable target) { init(null, target, "thread-" + nextthreadnum(), 0);}/** * 创建一个指定所属线程组和runnable的线程 * 其中name规则为 "thread-" + nextthreadnum() */public thread(threadgroup group, runnable target) { init(group, target, "thread-" + nextthreadnum(), 0);}/** * 创建一个指定name线程 */public thread(string name) { init(null, null, name, 0);}/** * 创建一个指定所属线程组和name的线程 */public thread(threadgroup group, string name) { init(group, null, name, 0);}/** * 创建一个指定runnable和name的线程 */public thread(runnable target, string name) { init(null, target, name, 0);}/** * allocates a new {@code thread} object so that it has {@code target} * as its run object, has the specified {@code name} as its name, * and belongs to the thread group referred to by {@code group}. * 创建一个新的thread对象，同时满足以下条件： * 1.该线程拥有一个指定的runnable对象用于方法执行 * 2.该线程具有一个指定的名称 * 3.该线程属于一个指定的线程组threadgroup * <p>if there is a security manager, its * {@link securitymanager#checkaccess(threadgroup) checkaccess} * method is invoked with the threadgroup as its argument. * 若这里有个安全管理器，则threadgroup将调用checkaccess方法进而触发securitymanager的checkaccess方法 * <p>in addition, its {@code checkpermission} method is invoked with * the {@code runtimepermission("enablecontextclassloaderoverride")} * permission when invoked directly or indirectly by the constructor of a subclass which * overrides the {@code getcontextclassloader} or {@code setcontextclassloader} methods. * 当enablecontextclassloaderoverride被开启时，checkpermission将被重写子类直接或间接地调用 * <p>the priority of the newly created thread is set equal to the * priority of the thread creating it, that is, the currently running * thread. the method {@linkplain #setpriority setpriority} may be * used to change the priority to a new value. * 新创建的thread的优先级等同于创建它的线程的优先级，调用setpriority会变更其优先级 * <p>the newly created thread is initially marked as being a daemon * thread if and only if the thread creating it is currently marked * as a daemon thread. the method {@linkplain #setdaemon setdaemon} * may be used to change whether or not a thread is a daemon. * 当且仅当线程创建时被显示地标记为守护线程，新创建的线程才会被初始化为一个守护线程 * setdaemon方法可以设置当前线程是否为守护线程 */public thread(threadgroup group, runnable target, string name) { init(group, target, name, 0);}/** * allocates a new {@code thread} object so that it has {@code target} as its run object, * has the specified {@code name} as its name, and belongs to the thread group referred to * by {@code group}, and has the specified <i>stack size</i>. * 创建一个新的thread对象，同时满足以下条件： * 1.该线程拥有一个指定的runnable对象用于方法执行 * 2.该线程具有一个指定的名称 * 3.该线程属于一个指定的线程组threadgroup * 4.该线程拥有一个指定的栈容量 * <p>this constructor is identical to {@link #thread(threadgroup,runnable,string)} * with the exception of the fact that it allows the thread stack size to be specified. * the stack size is the approximate number of bytes of address space that the virtual machine * is to allocate for this thread's stack. <b>the effect of the {@code stacksize} parameter, * if any, is highly platform dependent.</b> * 栈容量指的是jvm分配给该线程的栈的地址(内存)空间大小，这个参数的效果高度依赖于jvm运行平台 * <p>on some platforms, specifying a higher value for the {@code stacksize} parameter may allow * a thread to achieve greater recursion depth before throwing a {@link stackoverflowerror}. * similarly, specifying a lower value may allow a greater number of threads to exist * concurrently without throwing an {@link outofmemoryerror} (or other internal error). * the details of the relationship between the value of the <tt>stacksize</tt> parameter * and the maximum recursion depth and concurrency level are platform-dependent. * <b>on some platforms, the value of the {@code stacksize} parameter * may have no effect whatsoever.</b> * 在一些平台上，栈容量越高,(会在栈溢出之前)允许线程完成更深的递归(换句话说就是栈空间更深) * 同理，若栈容量越小，(在抛出内存溢出之前)允许同时存在更多的线程数 * 对于栈容量、最大递归深度和并发水平之间的关系依赖于平台 * <p>the virtual machine is free to treat the {@code stacksize} parameter as a suggestion. * if the specified value is unreasonably low for the platform,the virtual machine may instead * use some platform-specific minimum value; if the specified value is unreasonably high, * the virtual machine may instead use some platform-specific maximum. * likewise, the virtual machine is free to round the specified value up or down as it sees fit * (or to ignore it completely). * jvm会将指定的栈容量作为一个参考依据，但当小于平台最小值时会直接使用最小值，最大值同理 * 同样，jvm会动态调整栈空间的大小以适应程序的运行或者甚至直接就忽视该值的设置 * <p><i>due to the platform-dependent nature of the behavior of this constructor, extreme care * should be exercised in its use.the thread stack size necessary to perform a given computation * will likely vary from one jre implementation to another. in light of this variation, * careful tuning of the stack size parameter may be required,and the tuning may need to * be repeated for each jre implementation on which an application is to run.</i> * 简单总结一下就是：这个值严重依赖平台，所以要谨慎使用，多做测试验证 * @param group * the thread group. if {@code null} and there is a security * manager, the group is determined by {@linkplain * securitymanager#getthreadgroup securitymanager.getthreadgroup()}. * if there is not a security manager or {@code * securitymanager.getthreadgroup()} returns {@code null}, the group * is set to the current thread's thread group. * 当线程组为null同时有个安全管理器，该线程组由securitymanager.getthreadgroup()决定 * 当没有安全管理器或getthreadgroup为空，该线程组即为创建该线程的线程所属的线程组 * @param target * the object whose {@code run} method is invoked when this thread * is started. if {@code null}, this thread's run method is invoked. * 若该值为null，将直接调用该线程的run方法（等同于一个空方法） * @param name * the name of the new thread * @param stacksize * the desired stack size for the new thread, or zero to indicate * that this parameter is to be ignored. * 当栈容量被设置为0时，jvm就会忽略该值的设置 * @throws securityexception * if the current thread cannot create a thread in the specified thread group * 如果当前线程在一个指定的线程组中不能创建一个新的线程时将抛出 安全异常 * @since 1.4 */public thread(threadgroup group, runnable target, string name,long stacksize) { init(group, target, name, stacksize);} |
■ 重要变量
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
//线程名，用char来保存（string底层实现就是char）private char name[];//线程优先级private int priority;//不明觉厉private thread threadq;//不明觉厉private long eetop;/* whether or not to single_step this thread. 不明觉厉*/private boolean single_step;/* whether or not the thread is a daemon thread. 是否是守护线程，默认非守护线程*/private boolean daemon = false;/* jvm state. 是否一出生就领便当，默认false*/private boolean stillborn = false;/* what will be run. thread的run方法最终会调用target的run方法*/private runnable target;/* the group of this thread. 当前线程的所属线程组*/private threadgroup group;/* the context classloader for this thread 当前线程的classloader*/private classloader contextclassloader;/* the inherited accesscontrolcontext of this thread 当前线程继承的accesscontrolcontext*/private accesscontrolcontext inheritedaccesscontrolcontext;/* for autonumbering anonymous threads. 给匿名线程自动编号，并按编号起名字*/private static int threadinitnumber;/* threadlocal values pertaining to this thread. this map is maintained by the threadlocal class. * 当前线程附属的threadlocal，而threadlocalmap会被threadlocal维护（threadlocal会专门分析） */threadlocal.threadlocalmap threadlocals = null;/* * inheritablethreadlocal values pertaining to this thread. this map is * maintained by the inheritablethreadlocal class. * 主要作用：为子线程提供从父线程那里继承的值 * 在创建子线程时，子线程会接收所有可继承的线程局部变量的初始值，以获得父线程所具有的值 * 创建一个线程时如果保存了所有 inheritablethreadlocal 对象的值，那么这些值也将自动传递给子线程 * 如果一个子线程调用 inheritablethreadlocal 的 get() ，那么它将与它的父线程看到同一个对象 */ threadlocal.threadlocalmap inheritablethreadlocals = null;/* * the requested stack size for this thread, or 0 if the creator did not specify a stack size. * it is up to the vm to do whatever it likes with this number; some vms will ignore it. * 栈容量：当设置为0时，jvm会忽略该值；该值严重依赖于jvm平台，有些vm甚至会直接忽视该值 * 该值越大，线程栈空间变大，允许的并发线程数就越少；该值越小，线程栈空间变小，允许的并发线程数就越多 */private long stacksize;/* jvm-private state that persists after native thread termination.*/private long nativeparkeventpointer;/* thread id. 每个线程都有专属id，但名字可能重复*/private long tid;/* for generating thread id 用于id生成，每次+1*/private static long threadseqnumber;/* * java thread status for tools,initialized to indicate thread 'not yet started' * 线程状态 0仅表示已创建 */private volatile int threadstatus = 0;/** * the argument supplied to the current call to java.util.concurrent.locks.locksupport.park. * set by (private) java.util.concurrent.locks.locksupport.setblocker * accessed using java.util.concurrent.locks.locksupport.getblocker * 主要是提供给 java.util.concurrent.locks.locksupport该类使用 */volatile object parkblocker;/* the object in which this thread is blocked in an interruptible i/o operation, if any. * the blocker's interrupt method should be invoked after setting this thread's interrupt status. * 中断阻塞器：当线程发生io中断时，需要在线程被设置为中断状态后调用该对象的interrupt方法 */private volatile interruptible blocker;//阻塞器锁，主要用于处理阻塞情况private final object blockerlock = new object(); /* the minimum priority that a thread can have. 最小优先级*/public final static int min_priority = 1;/* the default priority that is assigned to a thread. 默认优先级*/public final static int norm_priority = 5;/* for generating thread id 最大优先级*/public final static int max_priority = 10;/* 用于存储堆栈信息 默认是个空的数组*/private static final stacktraceelement[] empty_stack_trace = new stacktraceelement[0];private static final runtimepermission subclass_implementation_permission = new runtimepermission("enablecontextclassloaderoverride");// null unless explicitly set 线程异常处理器，只对当前线程有效private volatile uncaughtexceptionhandler uncaughtexceptionhandler;// null unless explicitly set 默认线程异常处理器，对所有线程有效private static volatile uncaughtexceptionhandler defaultuncaughtexceptionhandler; |
■ 本地方法
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
/* * make sure registernatives is the first thing <clinit> does. * 确保clinit最先调用该方法：所有该方法是类中的最靠前的一个静态方法 * clinit：在jvm第一次加载class文件时调用，用于静态变量初始化语句和静态块的执行 * 所有的类变量初始化语句和类型的静态初始化语句都被java编译器收集到该方法中 * * registernatives方法被native修饰，即是本地方法，将由c/c++去完成，并被编译成了.dll，供java调用 * 其主要作用是将c/c++中的方法映射到java中的native方法，实现方法命名的解耦 */private static native void registernatives();static { registernatives();}/** 主动让出cpu资源,当时可能又立即抢到资源 **/public static native void yield();/** 休眠一段时间，让出资源但是并不会释放对象锁 **/public static native void sleep(long millis) throws interruptedexception;/** 检查 线程是否存活 **/public final native boolean isalive();/** 检查线程是否中断 isinterrupted() 内部使用 **/private native boolean isinterrupted(boolean clearinterrupted);/** 返回当前执行线程 **/public static native thread currentthread();public static native boolean holdslock(object obj);private native void start0();private native void setpriority0(int newpriority);private native void stop0(object o);private native void suspend0();private native void resume0();private native void interrupt0();private native void setnativename(string name); |
■ 线程初始化
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
/** * initializes a thread. * 初始化一个线程 * @param g the thread group * @param target the object whose run() method gets called * @param name the name of the new thread * @param stacksize the desired stack size for the new thread, or * zero to indicate that this parameter is to be ignored. */private void init(threadgroup g, runnable target, string name,long stacksize) { if (name == null) { throw new nullpointerexception("name cannot be null"); } //返回当前线程，即创建该hread的线程 currentthread是个本地方法 thread parent = currentthread(); //安全管理器根据java安全策略文件决定将哪组权限授予类 //如果想让应用使用安全管理器和安全策略，可在启动jvm时设定-djava.security.manager选项 //还可以同时指定安全策略文件 //如果在应用中启用了java安全管理器，却没有指定安全策略文件，那么java安全管理器将使用默认的安全策略 //它们是由位于目录$java_home/jre/lib/security中的java.policy定义的 securitymanager security = system.getsecuritymanager(); if (g == null) { /* determine if it's an applet or not */ /* if there is a security manager, ask the security manager what to do. */ if (security != null) { g = security.getthreadgroup(); } /* if the security doesn't have a strong opinion of the matter use the parent thread group. */ if (g == null) { g = parent.getthreadgroup(); } } /* checkaccess regardless of whether or not threadgroup is explicitly passed in. */ //判断当前运行线程是否有变更其线程组的权限 g.checkaccess(); if (security != null) { if (isccloverridden(getclass())) { security.checkpermission(subclass_implementation_permission); } } //新建线程数量计数+1 或者说未就绪线程数+1==> nunstartedthreads++; g.addunstarted(); this.group = g; this.daemon = parent.isdaemon();//若当前运行线程是守护线程，新建线程也是守护线程 this.priority = parent.getpriority();//默认使用当前运行线程的优先级 this.name = name.tochararray(); //设置contextclassloader if (security == null || isccloverridden(parent.getclass())) this.contextclassloader = parent.getcontextclassloader(); else this.contextclassloader = parent.contextclassloader; this.inheritedaccesscontrolcontext = accesscontroller.getcontext(); this.target = target; setpriority(priority);//若有指定的优先级，使用指定的优先级 if (parent.inheritablethreadlocals != null) this.inheritablethreadlocals = threadlocal.createinheritedmap(parent.inheritablethreadlocals); /* stash the specified stack size in case the vm cares */ this.stacksize = stacksize; /* set thread id 线程安全，序列号每次同步+1*/ tid = nextthreadid();}private static synchronized long nextthreadid() { return ++threadseqnumber;} |
■ start 方法
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
/** * causes this thread to begin execution; the java virtual machine * calls the <code>run</code> method of this thread. * 线程进入就绪态，随后jvm将会调用这个线程run方法 * 当获取到cpu时间片时，会立即执行run方法，此时线程会直接变成运行态 * <p> * the result is that two threads are running concurrently: the * current thread (which returns from the call to the * <code>start</code> method) and the other thread (which executes its * <code>run</code> method). * <p> * it is never legal to start a thread more than once. * in particular, a thread may not be restarted once it has completed execution. * 一个线程只能被start一次，特别是线程不会在执行完毕后重新start * 当线程已经start了，再次执行会抛出illegalthreadstateexception异常 * @exception illegalthreadstateexception if the thread was already started. * @see #run() * @see #stop() */public synchronized void start() { /** * this method is not invoked for the main method thread or "system" * group threads created/set up by the vm. any new functionality added * to this method in the future may have to also be added to the vm. * 该方法不会被主线程或系统线程组调用，若未来有新增功能，也会被添加到vm中 * a zero status value corresponds to state "new". * 0对应"已创建"状态 -> 用常量或枚举标识多好 */ if (threadstatus != 0) throw new illegalthreadstateexception(); /* notify the group that this thread is about to be started * so that it can be added to the group's list of threads * and the group's unstarted count can be decremented. */ //通知所属线程组该线程已经是就绪状态，因而可以被添加到该线程组中 //同时线程组的未就绪线程数需要-1，对应init中的+1 group.add(this); boolean started = false; try { //调用本地方法，将内存中的线程状态变更为就绪态 //同时jvm会立即调用run方法,获取到cpu之后，线程变成运行态并立即执行run方法 start0(); started = true;//标记为已开启 } finally { try { if (!started) { group.threadstartfailed(this);//如果变更失败，要回滚线程和线程组状态 } } catch (throwable ignore) { /* do nothing. if start0 threw a throwable then it will be passed up the call stack */ //如果start0出错，会被调用栈直接通过 } }}-------------//start之后会立即调用run方法thread t = new thread( new runnable() { @override public void run() { system.out.println(thread.currentthread().getname()); }},"roman");t.start(); //roman |
■ run 方法
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
/** * if this thread was constructed using a separate <code>runnable</code> run object, * then that <code>runnable</code> object's <code>run</code> method is called; * otherwise, this method does nothing and returns. * subclasses of <code>thread</code> should override this method. * 若thread初始化时有指定runnable就执行其的run方法，否则donothing * 该方法必须被子类实现 */@overridepublic void run() { if (target != null) { target.run(); }} |
■ isalive 方法
|
1
2
3
4
5
6
7
8
9
|
/** * tests if this thread is alive. a thread is alive if it has * been started and has not yet died. * 测试线程是否处于活动状态 * 活动状态：线程处于正在运行或者准备开始运行状态 * @return <code>true</code> if this thread is alive; * <code>false</code> otherwise. */public final native boolean isalive(); |
✺ 线程运行 ： 模拟电梯运行类
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
public class liftoff implements runnable { private int countdown = 10; //电梯阶层// private static int taskcount = 0;// private final int id = taskcount++; public liftoff(){ } // syn countdown private synchronized int getcountdown(){ --countdown; return countdown; } // 获取电梯状态 public string status() { return thread.currentthread().tostring()+ "("+ (countdown > 0? countdown: "liftoff!") + "),"; } @override public void run(){ while (getcountdown() >0){ system.out.println(status()); thread.yield(); } } public static void main(string[] args) { // thread's start() thread thread = new thread(new liftoff()); thread.start(); // 调用 run() system.out.println("================waiting for liftoff...==========================="); }} |
线程都会有自己的名字
获取线程对象的方法： thread.currentthread()
目标 run() 结束后线程完成
jvm线程调度程序决定实际运行哪个处于可运行状态的线程
使用线程池执行处理任务
线程状态流程图：
■ sleep 方法
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
/** * causes the currently executing thread to sleep (temporarily cease execution) * for the specified number of milliseconds plus the specified number of nanoseconds, * subject to the precision and accuracy of system timers and schedulers. * the thread does not lose ownership of any monitors. * 使线程睡眠一段毫秒时间，但线程并不会丢失已有的任何监视器 */public static void sleep(long millis, int nanos) throws interruptedexception { if (millis < 0) { throw new illegalargumentexception("timeout value is negative"); } if (nanos < 0 || nanos > 999999) { throw new illegalargumentexception("nanosecond timeout value out of range"); } //换算用 if (nanos >= 500000 || (nanos != 0 && millis == 0)) { millis++; } sleep(millis);}/** 我们一般会直接调用native方法，这或许是我们主动使用的最多次的native方法了 **/public static native void sleep(long millis) throws interruptedexception; |
■ yield 方法
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
/** * a hint to the scheduler that the current thread is willing to yield * its current use of a processor. the scheduler is free to ignore this hint. * 暗示线程调度器当前线程将释放自己当前占用的cpu资源 * 线程调度器会自由选择是否忽视此暗示 * <p> yield is a heuristic attempt to improve relative progression * between threads that would otherwise over-utilise a cpu. its use * should be combined with detailed profiling and benchmarking to * ensure that it actually has the desired effect. * 该方法会放弃当前的cpu资源，将它让给其他的任务去占用cpu执行时间 * 但放弃的时间不确定，可能刚刚放弃又获得cpu时间片 * <p> it is rarely appropriate to use this method. it may be useful * for debugging or testing purposes, where it may help to reproduce * bugs due to race conditions. it may also be useful when designing * concurrency control constructs such as the ones in the * {@link java.util.concurrent.locks} package. * 该方法的适合使用场景比较少，主要用于debug，比如lock包设计 */public static native void yield(); |
■ interrupt 方法
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
/** * interrupts this thread. * 中断一个线程 * <p> unless the current thread is interrupting itself, which is always permitted, * the {@link #checkaccess() checkaccess} method of this thread is invoked, * which may cause a {@link securityexception} to be thrown. * 如果当前线程不是被自己中断，可能会抛出securityexception异常 * <p> if this thread is blocked in an invocation of the {@link object#wait() wait()}, * {@link object#wait(long) wait(long)}, or {@link object#wait(long, int) wait(long, int)} * methods of the {@link object} class, or of the {@link #join()}, {@link #join(long)}, {@link * #join(long, int)}, {@link #sleep(long)}, or {@link #sleep(long, int)},methods of this class, * then its interrupt status will be cleared and it will receive an {@link interruptedexception}. * 若当前线程已被object.wait()方法、thread的join()或sleep方法阻塞， * 则调用该中断方法会抛出interruptedexception同时中断状态会被清除 * <p> if this thread is blocked in an i/o operation upon an {@link * java.nio.channels.interruptiblechannel </code>interruptible channel<code>} * then the channel will be closed, the thread's interrupt status will be set, * and the thread will receive a {@link java.nio.channels.closedbyinterruptexception}. * 若当前线程在interruptiblechannel上发生io阻塞，该通道要被关闭并将线程状态设置为中断同时抛出 * closedbyinterruptexception异常 * <p> if this thread is blocked in a {@link java.nio.channels.selector} then the thread's * interrupt status will be set and it will return immediately from the selection operation, * possibly with a non-zero value, just as if the selector's {@link * java.nio.channels.selector#wakeup wakeup} method were invoked. * 若该线程被选择器阻塞，将线程状态设置为中断同时从选取方法中立即返回 * 该选取方法通常会返回一个非0值，当wakeup方法正好被调用时 * <p> if none of the previous conditions hold then this thread's interrupt status will be set. </p> * 非上述情况都会将线程状态设置为中断 * <p> interrupting a thread that is not alive need not have any effect. * 中断一个非活线程不会有啥影响 * @throws securityexception if the current thread cannot modify this thread * @revised 6.0 * @spec jsr-51 */public void interrupt() { if (this != thread.currentthread()) checkaccess(); synchronized (blockerlock) { interruptible b = blocker; if (b != null) { // just to set the interrupt flag // 调用interrupt方法仅仅是在当前线程中打了一个停止的标记，并不是真的停止线程！ interrupt0(); b.interrupt(this); return; } } interrupt0();} |
■ daemon
分类：在java中分成两种线程：用户线程和守护线程
特性：当进程中不存在非守护线程时，则全部的守护线程会自动化销毁
应用： jvm在启动后会生成一系列守护线程，最有名的当属gc（垃圾回收器）
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
thread t2 = new thread(new runnable() { @override public void run() { system.out.println("守护线程运行了"); for (int i = 0; i < 500000;i++){ system.out.println("守护线程计数：" + i); } }}, "kira");t2.setdaemon(true);t2.start();thread.sleep(500);-------------//输出：......守护线程计数：113755守护线程计数：113756守护线程计数：113757守护线程计数：113758//结束打印：会发现守护线程并没有打印500000次，因为主线程已经结束运行了 |
■ wait 和 notify 机制
wait()使线程停止运行，notify()使停止的线程继续运行
使用wait()、notify()、notifyall()需要先对调用对象加锁，即只能在同步方法或同步块中调用这些方法
调用wait()方法后，线程状态由running变成waiting，并将当前线程放入对象的等待队列中
调用notify()或notifyall()方法之后，等待线程不会从wait()返回，需要notify()方法所在同步块代码执行完毕而释放锁之后，等待线程才可以获取到该对象锁并从wait()返回
notify()方法将随机选择一个等待线程从等待队列中移到同步队列中；notifyall()方法会将等待队列中的所有等待线线程全部移到同步队列中，被移动线程状态由waiting变成blocked
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
// wait/notify 简单实例public class numberprint implements runnable { private int number; public byte[] res; public static int count = 5; public numberprint(int number, byte a[]){ this.number = number; res = a; } @override public void run() { synchronized (res){ while (count-- > 0){ try { res.notify(); //唤醒等待res资源的线程，把锁交给线程（该同步锁执行完毕自动释放锁） system.out.println(" " + number); res.wait(); //释放cpu控制权，释放res的锁，本线程阻塞，等待被唤醒 system.out.println("----------线程"+thread.currentthread().getname() + "获得锁，wait()后的代码继续运行："+ number); } catch (interruptedexception e) { e.printstacktrace(); } } //end of while return; } //syn } public static void main(string[] args) { final byte[] a = {0}; //以该对象为共享资源 new thread(new numberprint(1,a),"1").start(); new thread(new numberprint(2,a),"2").start(); }} |
*****各位看客，由于对线程的调度机制还理解比较浅，所以本文会持续更新…… ********
以上这篇浅谈多线程_让程序更高效的运行就是小编分享给大家的全部内容了，希望能给大家一个参考，也希望大家多多支持服务器之家。
原文链接：http://www.cnblogs.com/romanjoy/p/7280363.html
