Brian Jones wrote:
> You may wish to check that a "stillborn" thread has a null thread
> group after stop() has been called. I did confirm already that
> threads that run and are stopped are seen to have a null thread group.
The Sun JDK ignores stop() when called on an unstarted thread (and the
g
David Holmes <[EMAIL PROTECTED]> writes:
> > You may wish to check that a "stillborn" thread has a null thread
> > group after stop() has been called. I did confirm already that
> > threads that run and are stopped are seen to have a null
> > thread group.
>
> A thread is removed from its thread
> You may wish to check that a "stillborn" thread has a null thread
> group after stop() has been called. I did confirm already that
> threads that run and are stopped are seen to have a null
> thread group.
A thread is removed from its threadgroup only when the thread
terminates. If stop() is in
Jeroen Frijters <[EMAIL PROTECTED]> writes:
> > - You may need more lifecycle management in VMThread. For example, a
> > thread that has stop() called on it before it is started is
> > "stillborn".
>
> The docs do say that, but my tests suggest that Sun just ignores stop()
> when called on an uns
> Thanks for taking the time to comment!
No problem.
> > - You may need more lifecycle management in VMThread. For
> > example, a thread that has stop() called on it before it is
started is
> > "stillborn".
>
> The docs do say that, but my tests suggest that Sun just
> ignores stop() when called
Hi David,
Thanks for taking the time to comment!
David Holmes wrote:
> - Thread.VMThread and Thread.group must be volatile as they are
> accessed by multiple threads without synchronization via isAlive() -
> or else ensure everything that reads them only does so while holding
> the thread's lock.
6 matches
Mail list logo
