We have had the Digital JDK 1.1.6 on our 4.0D system for some time.
Recently, the "javac" program stopped working, and I'm at a loss to
understand why.
Specifically, it says:
**Out of memory, exiting**
when run with any number of arguments (including zero). I tried running
javac as root and raised the memory limits to pretty high numbers, but it
still gives that error message.
"java" and other JDK programs work fine.
The machine is an AlphaStation 500 running Digital 4.0D. We recently
upgraded to Patch Kit 3 and added a gigabit network card. After this
upgrade, javac was reported to be working okay, although I didn't see this
myself. Later on that week, I reconfigured the network card setup (as
regular readers may recall) and after this point, javac appears to have
stopped working.
I would be surprised if the network interface reconfiguration (all via
netconfig) had anything to do with javac failing. However, I remember
reports that under Windows, old versions of javac would cause modems to dial
the ISP in search of an internet connection.
I'm at a loss to understand what's wrong.
I installed the Java 1.2 Beta2 JDK in hopes that that would work, but still
no dice; the 1.2 Beta 2 javac returns the same error message. (The 1.2 and
1.1.6 are installed in wholly separate directories by default.)
I tried unsetting and setting environment variables, running as different
users, and a variety of other things, but still no dice.
Has anyone seen this behavior before? Is there a way I can use dbx or
something to find out exactly where javac is determining "no memory" and
giving up?
Thanks for your help,
--Pat McCormick
Received on Tue Apr 20 1999 - 20:23:51 NZST