Hi,
Thanks for your answers :-)
> One thing you might do is to file the error report to Sun, as hinted in
the crash log.
I did that immediately :-)
I have got no feedback from Sun, though... I hope it means that they
have fixed it already.
> Check the release notes of 1.6.0_02 JRE for the SIGSEGV details; it
> could even be fixed already.
The release notes for update 2 (on
http://java.sun.com/javase/6/webnotes/ReleaseNotes.html)
do not mention any such fix :-(
> there's quite a number of such threads
> (and to me at least it sounds
> strange to have that many timer threads).
I will definitely try to find out where all of this threads come from,
and fix it because I am quite sure I don't need that many. I mean, I
launch maybe 10 threads per minute, but they spend only a few seconds
(5 minutes maximum) in method run(), and I don't keep a reference to
them so they should be nullified and garbage collected right ? Or do I
need to explicitly stop them ?
Let's say method launchThread() creates and starts a thread T, then
exits without keeping any reference to thread T. When method run() of
thread T is over, is there any thing left to do ? Should I explicitly
destroy T or is it done automatically ?
Another thread creator suspect is a feature we have to regularly check
configuration files updates, I will try and disable this feature,
could be a bug with that, never know.
Thanks a lot !
Nicolas RAOUL
http://nrw.free.fr
|
