假设我有Task
提交给ExecutorService
的第三方Java库。
我相信第三方库不是恶意的,但是很可能存在编程错误导致它陷入无限循环,如果是这种情况,我无法修复它解决这些罕见的情况。
处理此问题的最佳方法是什么,以便应用程序也不会卡住? shutdownNow()
是否足以处理这种情况?
有一个相关的问题Stop an infinite loop in an ExecutorService task,但这取决于程序员合作并检测Thread.currentThread().isInterrupted()
停止处理的能力,这是我不能依赖的。
(在我的情况下,它是Jython代码;在早期版本的Jython the interpreter apparently didn't check Thread.currentThread().isInterrupted()
中,不确定它现在做什么......但我的问题对于任何第三方Java代码都是通用的。)
答案 0 :(得分:1)
如果任务有一个无限循环,不检查线程中断状态,并且不使用抛出InterruptedException
的方法,则shutdownNow()
不会停止它。
不允许程序完成的简单示例:
public static void main(String[] args) throws Exception {
ExecutorService e = Executors.newFixedThreadPool(1);
e.submit(() -> { while (true); });
e.shutdownNow();
System.out.println("Main is finished but the app keeps running");
}
一种方法是将线程作为守护进程运行:
public static void main(String[] args) throws Exception {
ExecutorService e = Executors.newFixedThreadPool(1, r -> {
Thread t = new Thread(r);
t.setDaemon(true);
return t;
});
e.submit(() -> { while (true); });
e.shutdownNow();
System.out.println("Main is finished and the app can exit");
}
答案 1 :(得分:1)
在我正确阅读了这个问题之后,我将这组课程整理在一起。相对简单:一个Runnable连接到套接字发送输入并从辅助jvm检索调用不稳定库的输出。
如果在3次尝试后没有收到任何反应,则会杀死次要的jvm。但它可以重新启动。辅助jvm有一个用于关闭插座的出口钩。
class SafetyValve implements Runnable{
PrintWriter out;
BufferedReader in;
Socket s = null;
AtomicBoolean flag;
SafetyValve(AtomicBoolean b){
flag = b;
}
@Override
public void run() {
try {
s = new Socket("localhost", 9000);
out = new PrintWriter(s.getOutputStream(), true);
in = new BufferedReader(new InputStreamReader(s.getInputStream()));
while (!Thread.currentThread().isInterrupted()){
flag.set(false);
out.print(0);
out.flush();
System.out.print(in.read());
flag.set(true);
}
} catch (Exception e) {
e.printStackTrace();
}
finally{
try {
s.close();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
}
Main / Controller类。它使用Thread类进行控制
public class Switch {
public static void main(String[] args) {
try {
AtomicBoolean flag = new AtomicBoolean(false);
int counter = 0;
ProcessBuilder pb = ...
pb.directory(,,,);
Process p = pb.start();
SafetyValve sv = new SafetyValve(flag);
Thread t = new Thread(sv);
t.start();
while(t.getState() != Thread.State.RUNNABLE){
Thread.sleep(10);
}
while(true){
if (flag.get() == false){
if (++counter == 3){
while(t.getState() != Thread.State.TERMINATED){
p.destroyForcibly();
t.interrupt();
Thread.sleep(10);
}
break;
}
}
else
counter = 0;
Thread.sleep(100);
}
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
辅助jvm有一个标准的服务器套接字实现:
class UnYielding{
int i = 0;
int returnInt(){
i++;
if (i > 2)
while(true);
return i;
}
}
class Hook extends Thread{
RunWild rw;
Hook(RunWild wr){
rw = wr;
}
public void run() {
try {
System.out.println("exit...");
System.out.flush();
rw.socket.close();
rw.server.close();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
public class RunWild {
ServerSocket server;
Socket socket;
RunWild(){
Runtime.getRuntime().addShutdownHook(new Hook(this));
}
public static void main(String[] args){
UnYielding u;
int i;
PrintWriter out;
BufferedReader in;
RunWild rw = new RunWild();
try {
rw.server = new ServerSocket(9000);
rw.socket = rw.server.accept();
out = new PrintWriter(rw.socket.getOutputStream(), true);
in = new BufferedReader(new InputStreamReader(rw.socket.getInputStream()));
u = new UnYielding();
while ((i = in.read()) != -1){
out.print(u.returnInt());
out.flush();
Thread.sleep(10);
System.out.print("waiting...");
System.out.flush();
}
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
我已经在OS X上测试了1.8,它按预期工作。如果需要这个不稳定的类,这是一种方法