Steve Byrne wrote:
> JDK 1.1.5 and 1.1.6 libc are built on a Debian 1.3.1 system -- no problems. My
> libc is 5.4.33, and libdl.so is libdl.so.1 => libdl.so.1.8.12.
? Then why won't it work on mine?
[research, research, test, grind, scratch head...]
AHA! A clue!
I started running java with all the lights on, maximum verbosity, and weird things
happened
like "can't find sun.tools.javac.Main". Lots of crashing and such. Unzipped and
rezipped the
classes.zip. Different classes can't be found. More head scratching. Then I checked my
classpath. Whoa! Lots of jars. Killed some - and now it works.
I suspect that somewhere between 1.1.3 and 1.1.5v7 some code (possible the javasoft
stuff) for loading things from jars got changed, and now it doesn't scale up to the
ridiculous proportions that I use. I built a tool for automagically building jars
using a
makefile-like syntax (it translates to a real makefile, actually). It enforces
dependencies,
so creates little subjars, then when done combines them into larger jars. I still
hadn't
removed the subjars, so there was some duplication and a big classpath with about 22
items,
including the packaged classes.zip, a source tree (.java files only), and a
destination tree
(.class files only).
Anyway, under 1.1.3 it worked, under 1.1.5v7 it barfed.
I found that the limit, at least on my machine, for trivial jars in a classpath is 254
- you
get "too many open files" errors after that. Interesting, but probably not relevant.
I'm still looking into depth issues, and trying to find a test example without
foisting all
my code off on you. But I thought perhaps sbb or others could peek at the source and
see if
all this rings a bell...
Thanks for help-
--
Paul Reavis [EMAIL PROTECTED]
Design Lead
Partner Software, Inc. http://www.partnersoft.com
