Re: one thread is created for each object construction?

From:

Mark Space <markspace@sbc.global.net>

Newsgroups:

comp.lang.java.programmer

Date:

Thu, 23 Aug 2007 18:17:22 GMT

Message-ID:

<46CDCF3A.2020208@sbc.global.net>

Ishwor Gurung wrote:

Loosing some foundation here... Internally in the JVM, how is the object "e"
represented?

Google will help you here. Here's one page I found doing a search for
"java threads internals":

http://www.artima.com/insidejvm/ed2/jvm6.html

It'll well be an instance of a class in the heap but that's
not what I intended to ask. Apologies. What I wanted to ask (without
forking a seperate discussion thread :-) was how threading works at JVM
level.

There's no one way for all JVMs to implement threading. Sun left the
specification vague so that each platform can implement threads as it
sees fit.

Some hints here:

http://www.artima.com/insidejvm/ed2/jvm11.html

You should make and refine your own Google searches if you need more
information.

Yes, java will look like any other process to the OS. But how are different
_instances_ of different non-related class represented in JVM?

Bytes on the heap; sometimes bytes on the stack.

This seems
to point me to the assumption, that the classes are indeed executing as
threads in JVM.

No. Never. You seem to have a grave misunderstanding of JVMs and maybe
programming in general.

Yes, but how about in the JVM? Is there a tutorial on how JVM works
somewhere? Perhaps tucked neatly instead of Sun's
lengthy-full-of-mathematical-symbol ones? :P

Google is your friend.

http://www.google.com/search?q=java+threads+internals