I have some questions about threads and the JDK.  I've read the README
files and done some preliminary scouring of the 'net and list archives
to no avail, but I haven't dug too deeply, and have just subscribed to
this list, so forgive me if this is deeply covered elsewhere.

I have access to two identical dual P-II machines.  One has been running
RedHat 5.2 (glibc 2.0 based) upgraded to the 2.2 kernel, and one is a
"fresh" install of RedHat 6.0 (glibc 2.1 based).  I've noticed different
behaviour from both of them and am looking for some feedback as to what
the behaviours might mean.

On the glibc 2.0 machine, green threads work great with both 1.1.7-v3
and 1.2-pre2.  Native threads work ok, but performance is actually worse
than with green threads,  although, in either case I'm finding that
1.2-pre2 is appx 5x faster than 1.1.7-v3. (Also, I followed the
instructions on the Gimp site for installing the URW fonts so the font
errors that 1.2-pre2 reports would go away, and now I get no fonts at
all with 1.2-pre2.)

On the glibc2.1 machine, with both JDK 1.1.7-v3 and 1.2-pre2 and native
threads, _all_ java apps freeze immediately upon initialization.  In
other words, I type, 'java appname' and essentially nothing happens
except that the java interpreter loads from disk and loads the class
files.  When it tries to execute the app, it just sits there.  Green
threads with 1.1.7-v3 work ok, and green threads with 1.2-pre2 appear to
work ok, but I have not done extensive testing other than trying to
start up an app that just starts up a whole pile of threads all doing
not very much.

I've been using the only version of 1.1.7-v3 that I could find, which
seems to indicate that it was compiled on a glibc2.0 machine, so I'm not
surprised it doesn't work on the glibc2.1 machine using native threads,
however, I am using the "correct" versions of the 1.2-pre2 for the
libraries on the particular machines, which _does_ surprise me that it
doesn't work on glibc2.1 machine.

Now, on the glibc2.0 machine, where I _can_ get native threads to run,
I'm noticing that with neither 1.1.7-v3 nor 1.2-pre2 does the JDK
utilize more than a single processor.  I thought that the idea of using
native threads was to take advantage of as many processors as might be
in the machine?  Am I wrong, or is this a known issue with the Linux
port, or is this something else entirely?

I'm perfectly willing to test anything on either of these machines that
anyone would like tested if they think they might be able to resolve any
of these issues.
 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
With Microsoft products, failure is not           Derek Glidden
an option - it's a standard component.      http://3dlinux.org/
Choose your life.  Choose your            http://www.tbcpc.org/
future.  Choose Linux.              http://www.illusionary.com/


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

Reply via email to