The complete error is :
[INFO] connection attempt 1 to Netty-Client-storm6/132.228.28.164:6712 
scheduled to run in 0 ms
2016-07-04T17:14:21.811+0800 b.s.m.n.Client [ERROR] connection attempt 1 to 
Netty-Client-storm6/132.228.28.164:6712 failed: java.lang.RuntimeException: 
Returned channel was actually not established
2016-07-04T17:14:21.811+0800 b.s.m.n.Client [INFO] connection attempt 2 to 
Netty-Client-storm6/132.228.28.164:6712 scheduled to run in 1002 ms
2016-07-04T17:14:22.814+0800 b.s.m.n.Client [ERROR] connection attempt 2 to 
Netty-Client-storm6/132.228.28.164:6712 failed: java.lang.RuntimeException: 
Returned channel was actually not established
2016-07-04T17:14:22.814+0800 b.s.m.n.Client [INFO] connection attempt 3 to 
Netty-Client-storm6/132.228.28.164:6712 scheduled to run in 1004 ms
2016-07-04T17:14:23.819+0800 b.s.m.n.Client [ERROR] connection attempt 3 to 
Netty-Client-storm6/132.228.28.164:6712 failed: java.lang.RuntimeException: 
Returned channel was actually not established
2016-07-04T17:14:23.819+0800 b.s.m.n.Client [INFO] connection attempt 4 to 
Netty-Client-storm6/132.228.28.164:6712 scheduled to run in 1014 ms
2016-07-04T17:14:24.834+0800 b.s.m.n.Client [ERROR] connection attempt 4 to 
Netty-Client-storm6/132.228.28.164:6712 failed: java.lang.RuntimeException: 
Returned channel was actually not established
2016-07-04T17:14:24.835+0800 b.s.m.n.Client [INFO] connection attempt 5 to 
Netty-Client-storm6/132.228.28.164:6712 scheduled to run in 1019 ms

After the topology is up, this error messages keep showing in logs of some 
workers.

According to this post: 
http://stackoverflow.com/questions/30732178/storm-error-async-loop-died ,storm 
0.9.5 should solve this problem.  But the storm version I am using is 0.9.5 and 
this error seems not be solved on my side.

So what should I do to solve this problem?  Thx a  lot.

Regard,
Junfeng Chen

发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用

Reply via email to