Not much experience with netbeans specifically, but I'm sure you can 'see' all the threads in a debug session in the netbeans GUI. Suspend JVM and they're all frozen for your examination. Clicking on a stack frame will almost certainly bring up the code executing that was executing at that point in 'time'.
If code within the thread writes to the console console, their outputs will be serialized (not interlaced) That will affect thread behavior, but you'll be able to concurrently see them all operational. A better strategy would be to create thread specific buffers to store traces and output the after the fact, and track the order of events post mortem.
Remember, in practice, your system probably has only one thing actually going on at a time.
Perhaps neither of these is quite what you mean by "see". Could you clarify?
romram
ASKER
>>Perhaps neither of these is quite what you mean by "see". Could you clarify?
I want to get their starting and ending and the output they produced.
If code within the thread writes to the console console, their outputs will be serialized (not interlaced) That will affect thread behavior, but you'll be able to concurrently see them all operational. A better strategy would be to create thread specific buffers to store traces and output the after the fact, and track the order of events post mortem.
Remember, in practice, your system probably has only one thing actually going on at a time.
Perhaps neither of these is quite what you mean by "see". Could you clarify?