On Thursday 22 January 2009 12:59, Matthew Toseland wrote: > On Thursday 22 January 2009 03:58, Dennis Nezic wrote: > > > > My main point in my last post was a suggestion to have the error > > > > message more informative. As another example, have it output it's > > > > memory/cpu usage before it shuts itself down, in the case of the > > > > deadlock I mentioned. > > > > > > How do we get CPU usage from java? We can say how much memory is in > > > use, how many threads are running, get a thread dump... > > > > Well--if the node knows enough to say that it is in a deadlock, and if > > it still has enough control over itself to be able to shut itself down > > cleanly, surely there is something it can do to investigate itself > > before doing so? Currently the messages do not appear to be helping us > > at all. Before shutting itself down in such deadlocks/freezes, it should > > at least output a thread-dump, and it's memory stats, if not a > > deeper/clearer analysis of what in particular, within MessageCore or > > PacketSender, is causing the problem. > > I agree we could do a stack dump, I thought we did.
We do in fact do a thread/stack dump according to the code, assuming we're running under the wrapper. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20090122/c105a76e/attachment.pgp>
