this repeats very fast. maybe its a indication for whats going on.
(10:21:20 AM) dwd: I know exactly what that bug is, but it'll be tricky to trace it in Java. (10:21:52 AM) dwd: It's a session that's closed (see the read call returning zero), but we're not closing the socket, and so it's causing epoll() to return immediately.
And from what I can tell there is still a Bug with 100% CPU usage.
I did have a quick look with strace on the crazy thread:
read(217, "", 128) = 0 gettimeofday({1434534355, 485756}, NULL) = 0 gettimeofday({1434534355, 485798}, NULL) = 0 gettimeofday({1434534355, 485815}, NULL) = 0 epoll_wait(49, {{EPOLLIN|EPOLLERR|EPOLLHUP, {u32=217, u64=16704004399789244633}}}, 4096, 1000) = 1this repeats very fast. maybe its a indication for whats going on.
(10:21:20 AM) dwd: I know exactly what that bug is, but it'll be tricky to trace it in Java.
(10:21:52 AM) dwd: It's a session that's closed (see the read call returning zero), but we're not closing the socket, and so it's causing epoll() to return immediately.