> I've been running 5026 for about 15 hours now. So far the following have > occurred: > > On stderr: > > java.lang.NullPointerException > at > freenet.ConnectionHandler.innerProcess(ConnectionHandler.java:556) > at freenet.ConnectionHandler.process(ConnectionHandler.java:547) > at > freenet.transport.ReadSelectorLoop.beforeSelect(ReadSelectorLoop.java:113) > at > freenet.transport.AbstractSelectorLoop.loop(AbstractSelectorLoop.java:540) > at freenet.transport.ReadSelectorLoop.run(ReadSelectorLoop.java:419) > at java.lang.Thread.run(Thread.java:534)
I think I just committed a fix for this, Toad or someone might want to check it though. > There have been 5 of these thus far > > Also, these nice messages have been given to stderr: > Waited more than 200ms to dequeue, 11 in queue, 1552 millis since enqueued > last item, 89832 maximum waits so far - could indicate serious JVM bug. > Please report to [EMAIL PROTECTED] along with JVM and OS/kernel. > Waited more than 200ms to dequeue, 11 in queue, 1880 millis since enqueued > last item, 93864 maximum waits so far - could indicate serious JVM bug. > Please report to [EMAIL PROTECTED] along with JVM and OS/kernel. > > Right now, my node is stalled, using 100% cpu. I think that those two are related. When one or another thread is using 100% CPU (maybe a thread running at higher priority than others even) it will starve other threads of their CPU time, thereby causing the messages you see above. Then again.. I might be wrong, tell me if so. /N _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
