java crashing when load average is high

[Jon Kuster]

Hi Greg,

On Tue, 2005-04-26 at 17:10 -0600, Greg Lewis wrote:
> Hi Jon,
> 
> On Wed, Apr 20, 2005 at 11:10:00PM -0700, Jon Kuster wrote:
> > Native x86 1.4 went straight into the loop.  Native x86 1.5 immediately
> > segfaulted - even on `java -version`.  I removed all java-related ports
> > and linux ports, then reinstalled linux_base-8 and linux-sun-jdk14 and
> > tried to build jdk15 again.  That build hung.  I tried it again this
> > afternoon and somehow, it succeeded (after manual intervention when the
> > build craps out on a spectacularly long command, but I expected that).
> 
> Just exactly what was that manual intervention?  Did you split up the
> command that failed?

Yes, pretty much.  I don't have a log of the build on this machine.  I
think I have one on our Dell, but it's currently being shipped to the
colo, so I won't be able to get it to you for a few days (assuming it's
still there).

Here are the instructions Ernst Winter gave me that got me around this
hurdle:

-----------------------------Snip-------------------------------------
i had the same problem and solved it executing the last command which
caused the error manually. Looks like the error comes because it's a
very long command. Just put the command that comes between 'then' and
'fi' in a shell file and execute it manually in the directory
work/j2sre/make/java/java (I'm not seating now in my amd64 FreeBSD
computer but I think that was the directory). The compilation will go
on without any problem if you resume it afterwards with a 'make
build'. 
                                                                                
--                                                                              
J.V. Jordan
Try 'make build |& tee build.out' (if your shell is csh or tcsh)
or             
'make build 2>&1 | tee build.out' (if sh or bash). After the
error              
comes, edit build.out and you will see the command causing it
(takes            
about two pages). 
-----------------------------Snip-------------------------------------

I did just what that says.  After the build died, I found the then, and
the fi, and copied/pasted everything in between into a shell script and
ran it, then restarted the build. IIRC, the pasting process broke it up
into 4 lines or so.  Three were fairly short, but the 4th was in the
neighborhood of 25K or so, by ee's column count.  Once I regain access
to the machine, I'll send a copy of that shell script as well, if it's
still there.

-Jon