2012-10-29 46 views
0

这里是线程转储:修复327和535错误修复devoll问题以及Epoll?

"New I/O client worker #23-1" prio=3 tid=0x007c1400 nid=0x28bc runnable [0xed17f000..0xed17f920] 
java.lang.Thread.State: RUNNABLE 
at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method) 
at sun.nio.ch.DevPollArrayWrapper.poll(DevPollArrayWrapper.java:164) 
at sun.nio.ch.DevPollSelectorImpl.doSelect(DevPollSelectorImpl.java:68) 
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69) 
- locked <0xefd18e90> (a sun.nio.ch.Util$1) 
- locked <0xefd18e80> (a java.util.Collections$UnmodifiableSet) 
- locked <0xefd012d8> (a sun.nio.ch.DevPollSelectorImpl) 
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80) 
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:158) 
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) 
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
at java.lang.Thread.run(Thread.java:619) 

"device-factory-timer-114-thread-1" prio=3 tid=0x0092ac00 nid=0x28ba waiting on condition [0xedd7f000..0xedd7fc20] 
java.lang.Thread.State: WAITING (parking) 
at sun.misc.Unsafe.park(Native Method) 
- parking to wait for <0xefd01460> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) 
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) 
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925) 
at java.util.concurrent.DelayQueue.take(DelayQueue.java:160) 
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583) 
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576) 
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) 
at java.lang.Thread.run(Thread.java:619) 

这是颇为相似epoll的问题。如果问题已经解决,或者您有任何解决方案,请告诉我。

回答

0

如果您认为有问题,请打开包含所有必需信息的错误报告。

+0

嗨,诺曼,我为此创建了一个错误#696。 – Dushyanth

+0

在Netty 3.1.5中可以看到此问题。 最新版本3.5.X使用内部调用Epoll的DeadLockProofWorker。 3.1.5版本使用可能调用Devpoll的IoWorkerRunnable。 有人可以告诉netty3.5.7是否适用于3.1.5开发的代码?这些版本之间是否有任何API更改?我可以使用旧的代码与新的Netty 3.5.7没有任何改变? – Dushyanth

+0

有一些变化,但它们更可能不会影响大多数用户。我肯定会尝试升级,看看它是否修复。 3.1.5真的很老 –