Thanks for the info.  It's still a bit strange as to why so _many_
threads are started.  I
imaging a default thread poll is created to handle each task.   Thanks
also for the timely
response.

Dave

David Deal wrote:
>
> My apologies if this question has been raised in the past.  I couldn't

> locate any info on this topic at blackdown or on this mail list.

Thanks for checking the list, even though you didn't manage to guess the

lucky words to search :-).

Those aren't separate processes, they're all threads of the same process

- in Linux, lightweight threads take up process table entries, just like

heavyweight processes. There's no hard-and-fast way to identify them as
such, although running "top" and noticing that they all use exactly the
same amount of memory is a strong hint. (Another, more precise, way is
to compare /proc/<pid>/maps for multiple pids and notice that they're
identical.)

You don't see this weirdness when you run with green threads, because
green threads are emulated in user space rather than provided by the
kernel.

Nathan


> When I start java or rmregistry in native modeIget tons of child
> processes (on the order of 25 - 60).  Any idea why this is?
> Is this normal behavior?
>
> example:
> ddeal    31427 31403  0 Jul27 pts/7 00:00:02
> /usr/local/java/bin/i386/native_threads/rmiregistry
> ddeal    31428 31427  0 Jul27 pts/7 00:00:00
> /usr/local/java/bin/i386/native_threads/rmiregistry
> ddeal    31429 31427  0 Jul27 pts/7 00:00:00
> /usr/local/java/bin/i386/native_threads/rmiregistry
> ddeal    31430 31427  0 Jul27 pts/7 00:00:00
> /usr/local/java/bin/i386/native_threads/rmiregistry
> ...
> and so on
>
> Running:
> Redhat 6.0 i386
> >uname -a
> Linux mrstick 2.2.5-22 #1 Fri Jul 2 10:41:38 PDT 1999 i686 unknown
> >java -version
> java version "1.2"
> Classic VM (build Linux_JDK_1.2_pre-release-v2, native threads,
sunwjit)
>
> Thanks for any info or pointers.
>
> Dave


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to