OpenJDK 1.7 has issues versus linux-sun-jdk17

[Greg Lewis]

On Tue, Dec 23, 2014 at 09:42:45AM +0100, Jean-Yves Moulin wrote:
> > On 17 Dec 2014, at 21:55 , Paul Pathiakis via freebsd-java <freebsd-java at freebsd.org> wrote:
> > 
> >> # A fatal error has been detected by the Java Runtime Environment:
> >> #
> >> #  SIGSEGV (0xb) at pc=0x0000000803a4d4ae, pid=84602, tid=35353228288
> >> #
> >> # JRE version: OpenJDK Runtime Environment (7.0-b14) (build 1.7.0_71-b14)
> >> # Java VM: OpenJDK 64-Bit Server VM (24.71-b01 mixed mode bsd-amd64 compressed oops)
> >> # Problematic frame:
> >> # j  java.net.SocketException.<init>(Ljava/lang/String;)V+0
> >> #
> >> # Core dump written. Default location: /cores/core or core.84602
> >> 
> 
> Interesting, we are tracking exactly the same kind of issue (Segfault on SocketException.init) with our home made applications.
> 
> The same java binary runs fine on Linux-openjdk7 (Linux OS or FreeBSD OS).
> 
> Did you got a response from OpenJDK team ?

Late reply on this.  Is it possible to narrow this down to a simpler test
case than "set up OpenNMS and run it for ten minutes"?  I assume one has to
actually do more than just run it, since the exception is likely a result
of some kind of network traffic.

If not that, a wiki or something on how to set up OpenNMS and provoke the
problem would be a big help.

-- 
Greg Lewis                          Email   : glewis at eyesbeyond.com
Eyes Beyond                         Web     : http://www.eyesbeyond.com
Information Technology              FreeBSD : glewis at FreeBSD.org