Doug,
Thanks - your comments do provide a clue. We are running inside a
VMWare virtual machine. So, if it were bad physical RAM, then I think
the failure would occur at the VMWare level. In our case, the virtual
machine and host operating system are not reporting any problems. It is
the JVM running inside the guest OS that gives the segmentation fault.
So, sounds like we might have a problem with the way that our virtual
machine memory is configured.
Has anybody out there had problems with Maven and/or Java inside VMWare
causing segmentation faults?
-- Mark
Doug Douglass wrote:
Mark,
The only time I've seen a maven build trigger a JVM seg fault the problem
was due to bad server memory. It was low end hardware running CentOS and
hosted our Cruise Control install, amongst many other things. The seg faults
were intermittent.
HTH and good luck,
Doug
On Wed, Apr 30, 2008 at 3:54 PM, Mark Hansen <[EMAIL PROTECTED]>
wrote:
We are trying to get the maven build for our product working under
RedHat linux (running as a guest OS under VMWare). This build works
fine on Windows Vista and XP. But under RedHat it is causing a Java
segmentation fault. See attached log file for details.
Does anyone have any ideas about how we might get to the bottom of what
is causing this and fix it?
Here are some details about our environment.
Maven version 2.0.9
JDK 1.6.0_05
Red Hat Enterprise Linux AS release 4 (Nahant Update 6)
jvm_args: -Xms768m -Xmx768m -Xss2048k
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
