Java VM crashing when running Jenkins?

[Craig Rodrigues]

Hi,

I did the following:

(1)  Booted my 10.0R VM.

(2)  Update devel/jenkins port to 1.550

(3)  Updated java/openjdk7 port to openjdk-7.51.13,1

When I started Jenkins, I got an exception similar to the one reported here:
http://lists.freebsd.org/pipermail/freebsd-java/2014-February/010557.html

I killed Jenkins, and then:

(4)  Took the patch from
http://people.freebsd.org/~lwhsu/patch/openjdk7-PortConfig.diff

(5)  Rebuilt the java/openjdk7 port


When I started Jenkins, it came up properly.  However, after, I started a
job, it seemed to get "stuck".

I could not access the web interface.  If I ran truss on the java process,
I saw:

umtx_op(0x80064b0c8,0xf,0x0,0x18,0x7fffff3f5990,0x7fffff3f5990) ERR#60
'Operation timed out'
clock_gettime(4,{20923.561195436 })              = 0 (0x0)
gettimeofday({1392087771.531672 },0x0)           = 0 (0x0)
clock_gettime(4,{20923.562748319 })              = 0 (0x0)
gettimeofday({1392087771.532822 },0x0)           = 0 (0x0)
_umtx_op(0x80064b0c8,0xf,0x0,0x18,0x7fffff3f5990,0x7fffff3f5990) ERR#60
'Operation timed out'
clock_gettime(4,{20923.626755758 })              = 0 (0x0)
gettimeofday({1392087771.597078 },0x0)           = 0 (0x0)
clock_gettime(4,{20923.630092903 })              = 0 (0x0)
gettimeofday({1392087771.602494 },0x0)           = 0 (0x0)
_umtx_op(0x80064b0c8,0xf,0x0,0x18,0x7fffff3f5990,0x7fffff3f5990) ERR#60
'Operation timed out'
clock_gettime(4,{20923.700019930 })              = 0 (0x0)
gettimeofday({1392087771.670213 },0x0)           = 0 (0x0)
clock_gettime(4,{20923.701298257 })              = 0 (0x0)
gettimeofday({1392087771.671372 },0x0)           = 0 (0x0)
_umtx_op(0x80064b0c8,0xf,0x0,0x18,0x7fffff3f5990,0x7fffff3f5990) ERR#60
'Operation timed out'
clock_gettime(4,{20923.769135582 })              = 0 (0x0)
gettimeofday({1392087771.740338 },0x0)           = 0 (0x0)
clock_gettime(4,{20923.771744310 })              = 0 (0x0)
gettimeofday({1392087771.741894 },0x0)           = 0 (0x0)


Any ideas what the problem could be?
Should I switch back to openjdk6?

--
Craig