Understanding java's native threads and the jvm
Posted
by Moev4
on Stack Overflow
See other posts from Stack Overflow
or by Moev4
Published on 2010-04-16T14:01:40Z
Indexed on
2010/04/16
14:03 UTC
Read the original article
Hit count: 179
I understand that the jvm is itself an application that turns the bytecode of the java executable into native machine code, but when using native threads I have some questions that I just cannot seem to answer.
- Does every thread create their own instance of the jvm to handle their particular execution?
- If not then does the jvm have to have some way to schedule which thread it will handle next, if so wouldn't this render the multi-threaded nature of java useless since only one thread can be ran at a time?
© Stack Overflow or respective owner