java 多线程饥饿现象的问题解决方法
锺威
本文向大家介绍java 多线程饥饿现象的问题解决方法，包括了java 多线程饥饿现象的问题解决方法的使用技巧和注意事项，需要的朋友参考一下
java 多线程饥饿现象的问题解决方法
当有线程正在读的时候，不允许写 线程写，但是允许其他的读线程进行读。有写线程正在写的时候，其他的线程不应该读写。为了防止写线程出现饥饿现象，当线程正在读，如果写线程请求写，那么应该禁止再来的读线程进行读。
实现代码如下：
File.Java
package readerWriter;
public class File {
private String name;
public File(String name)
{
this.name=name;
}
}
Pool.java
package readerWriter;
public class Pool {
private int readerNumber=0;
private int writerNumber=0;
private boolean waittingWriten;
public boolean isWaittingWriten() {
return waittingWriten;
}
public void setWaittingWriten(boolean waittingWriten) {
this.waittingWriten = waittingWriten;
}
public File getFile() {
return file;
}
public void setFile(File file) {
this.file = file;
}
File file;
public Pool(File file)
{
this.file=file;
}
public int getReaderNumber() {
return readerNumber;
}
public void setReaderNumber(int readerNumber) {
this.readerNumber = readerNumber;
}
public int getWriterNumber() {
return writerNumber;
}
public void setWriterNumber(int writerNumber) {
this.writerNumber = writerNumber;
}
}
Reader.java
package readerWriter;
public class Reader implements Runnable{
private String id;
private Pool pool;
public Reader(String id,Pool pool)
{
this.id=id;
this.pool=pool;
}
@Override
public void run()
{
// TODO Auto-generated method stub
while(!Thread.currentThread().interrupted()){
synchronized(pool){
while(pool.getWriterNumber()>0 || pool.isWaittingWriten()==true)//当线程正在写或者
//有线程正在等待写，则禁止读线程继续读
{
try {
pool.wait();
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
{
pool.setReaderNumber(pool.getReaderNumber()+1);
}
}
System.out.println(id+" "+"is reading....");
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
synchronized(pool)
{
pool.setReaderNumber(pool.getReaderNumber()-1);
System.out.println(id+" "+"is existing the reader....");
if(pool.getReaderNumber()==0)
pool.notifyAll();
} try {
Thread.sleep(1000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
// pool.notifyAll();
}
}
}
Writer.java
package readerWriter;
public class Writer implements Runnable{
private Pool pool;
String id;
public Writer(String id,Pool pool)
{
this.id=id;
this.pool=pool;
}
@Override
public void run() {
// TODO Auto-generated method stub
while(!Thread.currentThread().interrupted()){
synchronized(pool){
if(pool.getReaderNumber()>0)
pool.setWaittingWriten(true);
else
pool.setWaittingWriten(false);
//当线程正在被读或者被写或者有线程等待读
while(pool.getWriterNumber()>0 || pool.getReaderNumber()>0)
{
try {
pool.wait();
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
pool.setWaittingWriten(false); //这个策略还算公平
{
pool.setWriterNumber(pool.getWriterNumber()+1);
}
}
System.out.println(id+" "+"is writing....");
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
//
synchronized(pool)
{
pool.setWriterNumber(pool.getWriterNumber()-1);
System.out.println(id+" "+"is existing the writer....");
pool.notifyAll();
}
/* try {
Thread.sleep(1000);
//System.out.println("writer sleeping over");
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} */
}
}
}
Main.java
package readerWriter;
public class Main {
public static void main(String[] args) {
// TODO Auto-generated method stub
Pool pool=new Pool(new File("dd file"));
for(int i=0;i<2;i++)
{
Thread writer=new Thread(new Writer("writer "+i,pool));
writer.start();
}
for(int i=0;i<5;i++)
{
Thread reader=new Thread(new Reader("reader "+i,pool));
reader.start();
}
}
}
程序部分运行结果如下：
writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... reader 0 is reading.... reader 0 is existing the reader.... writer 1 is writing.... writer 1 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... reader 3 is reading.... reader 2 is reading.... reader 4 is reading.... reader 1 is reading.... reader 0 is reading.... reader 3 is existing the reader.... reader 1 is existing the reader.... reader 0 is existing the reader.... reader 4 is existing the reader.... reader 2 is existing the reader.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 1 is writing.... writer 1 is existing the writer.... reader 2 is reading.... reader 2 is existing the reader.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing.... writer 0 is existing the writer.... writer 0 is writing....
感谢阅读，希望能帮助到大家，谢谢大家对本站的支持！
类似资料：
-
从操作系统概念 5.8.2使用显示器的餐饮哲学家解决方案 接下来，我们通过对用餐哲学家问题提出一个无死锁的解决方案来说明监控概念。这个解决方案施加了一个限制，即哲学家只有在筷子都可用的情况下才能拿起筷子。为了给这个解决方案编码，我们需要区分我们可能找到哲学家的三种状态。为此，我们引入以下数据结构： 哲学家只有当她的两个邻居不吃饭时，我才能设置变量
-
本文向大家介绍Java多线程的临界资源问题解决方案，包括了Java多线程的临界资源问题解决方案的使用技巧和注意事项，需要的朋友参考一下 这篇文章主要介绍了Java多线程的临界资源问题解决方案,文中通过示例代码介绍的非常详细，对大家的学习或者工作具有一定的参考学习价值,需要的朋友可以参考下 临界资源问题的原因：某一个线程在对临界资源进行访问时，还没来得及完全修改临界资源的值，临界资源就被其他线程拿去
-
我已经完成了解决方案。因为在某个时间点，典型的监视器实现会导致饥饿。我已经阅读了这里给出的用餐哲学家问题的“礼貌”版本 那么，如果两个相邻的哲学家同时感到饥饿呢。因为测试（i）是检查它的左派和右派哲学家是否饿了。如果它发现它的邻居也饿了。这是一种僵局，对吗？我的意思是他们两个都不能吃东西，因为他们附近的哲学家家饿了，对吧？
-
本文向大家介绍如何解决PHP无法实现多线程的问题，包括了如何解决PHP无法实现多线程的问题的使用技巧和注意事项，需要的朋友参考一下 有没有办法在PHP中实现多线程呢？假设你正在写一个基于多台服务器的PHP应用，理想的情况时同时向多台服务器发送请求，而不是一台接一台。可以实现吗？当有人想要实现并发功能时，他们通常会想到用fork或者spawn threads，但是当他们发现PHP不支持多线程的时候，
-
我对这段代码有一个问题。这是典型的读者-作家问题。我按照这个维基百科页面上的伪代码找到了第一个让作者挨饿的问题。我想知道我实际上是如何注意到作家们正在挨饿的。 我试着把shared_variable的打印声明放在不同的地方，但这并没有给我太多的洞察力。但也许我只是不明白发生了什么。有人能向我解释一下我是如何直观地看到饥饿发生的吗？谢谢你！读取器或写入器尝试读取或写入的次数作为命令行参数给出。
-
我对和使用了RXJava。我知道他们不是在一条流上并行化排放。换句话说，单个排放流只会放在一个线程上，对吗？我下面的测试似乎表明了这一点。我的理解是，您还必须调度器，如，以在单个流上并行化发射。 同样，如果是这种情况，那么调度器会发生线程饥饿吗？如果我的计算调度程序有5个线程，但我有超过5个长时间运行的异步流正在处理，有没有可能出现饥饿？或者这不太可能仅仅是因为RXJava的性质？