> On Sunday 17 August 2003 02:44 pm, Niklas Bergh wrote: > > > 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. > > This makes sense biased on what I've seen. I previously reported my node using > 100% CPU, but I've just noticed that this does not start until AFTER that > same Null Pointer Exception appears.
So it might be the NPE that caused CPU load (and the CPU load that caused those 'Possible JVM bug' messages). If the NPE was the problem then the problem should be gone with latest unstable CVS I think (I haven't had the problem occur again with my node after the fix but sometimes it can take hours for it to occur so...). The NPE was due to a race between transfering data over a connection and terminating it... /N _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
