我寻思这那边也有微软嘛

WH 招人工智障不

那就送她拯救者吧

差不多吧，这是可以报销吗

@cmai 不是很明白，因为 jvm 何时刷新根据 cpu 指令之间的交互、cpu 调度等多种情况，具体你可能要看 jvm 源码了

你把 flag 定义 volatile 试下，我怀疑是子线程修改后没有及时刷新到主内存。

算了 这个排版贼鸡儿恶心

不存在你想的那个问题，设备上报的数据是通过 decoder 是 ChannelInbound 的 handler，你下发的数据 write 是通过 ChannelHandlerContext 写入 ChannelOutbound。下面是官方的图

I/O Request
via Channel or
ChannelHandlerContext
|
+---------------------------------------------------+---------------+
| ChannelPipeline | |
| \|/ |
| +---------------------+ +-----------+----------+ |
| | Inbound Handler N | | Outbound Handler 1 | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
| | \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler N-1 | | Outbound Handler 2 | |
| +----------+----------+ +-----------+----------+ |
| /|\ . |
| . . |
| ChannelHandlerContext.fireIN_EVT() ChannelHandlerContext.OUT_EVT()|
| [ method call] [method call] |
| . . |
| . \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler 2 | | Outbound Handler M-1 | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
| | \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler 1 | | Outbound Handler M | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
+---------------+-----------------------------------+---------------+
| \|/
+---------------+-----------------------------------+---------------+
| | | |
| [ Socket.read() ] [ Socket.write() ] |
| |
| Netty Internal I/O Threads (Transport Implementation) |
+-------------------------------------------------------------------+

@beingbin 看来我不配做个普通人

@alalida 刚看了下大盘今天涨的还可以

@dot2 今天可以回一波了吧

对啊 再等等就 2020 年了 哈哈哈哈

先考个项目管理吧

武汉呢

首先你的两个线程是持有同一个 test 对象来分别调用 write 和 read 方法？如果是那肯定非线程安全，如果是持有 new 的两个 test 对象，那就没影响了

复制黏贴
123
true
33

Process finished with exit code 0
修改 catch 代码块抛出异常
} catch (Exception e) {
e.printStackTrace();
}
结果：
java.util.concurrent.CancellationException
at java.util.concurrent.FutureTask.report(FutureTask.java:121)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at cmdt.minibus.model.MainClass.main(MainClass.java:17)
--------------------
源码：
设置 cancel，state 修改

public boolean cancel(boolean mayInterruptIfRunning) {
if (!(state == NEW &&
UNSAFE.compareAndSwapInt(this, stateOffset, NEW,
mayInterruptIfRunning ? INTERRUPTING : CANCELLED)))
return false;
try { // in case call to interrupt throws exception
if (mayInterruptIfRunning) {
try {
Thread t = runner;
if (t != null)
t.interrupt();
} finally { // final state
UNSAFE.putOrderedInt(this, stateOffset, INTERRUPTED);
}
}
} finally {
finishCompletion();
}
return true;
}

result.get 源码：
public V get() throws InterruptedException, ExecutionException {
int s = state;
if (s <= COMPLETING)
s = awaitDone(false, 0L);
return report(s);
}

private V report(int s) throws ExecutionException {
Object x = outcome;
if (s == NORMAL)
return (V)x;
if (s >= CANCELLED)
throw new CancellationException();
throw new ExecutionException((Throwable)x);
}
-----------
这里 result.cancel(false); 将线程终止，修改任务状态 state，后来执行 result.get()根据 state 状态已关闭抛出异常

想起来一次代码走查，用 lambda 写的代码讲了半天（雾）