Date: Wed, 20 Jun 2012 10:21:26 +0200 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: freebsd-java@freebsd.org Subject: Re: JVM crash in [libnet.so+0x9243] Java_java_net_SocketInputStream_socketRead0+0xb3 Message-ID: <op.wf6z50q68527sy@ronaldradial.versatec.local> In-Reply-To: <E3DA74B5-AE55-48EF-83B4-B34C7F1D3E65@gmail.com> References: <E3DA74B5-AE55-48EF-83B4-B34C7F1D3E65@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
First upgrade Tomcat. Your version is from Jan 2010 [1] or earlier. There are a lot of bugfixes in Tomcat about NIO since then. And also for security reasons [2]. Tomcat 6.0.35 is also in ports. Second, can you reproduce this with openjdk 6? Do you write hundreds of files per second or per day? Ronald. [1] http://tomcat.apache.org/tomcat-6.0-doc/changelog.html [2] http://tomcat.apache.org/security-6.html On Tue, 19 Jun 2012 23:13:15 +0200, Kees Jan Koster <kjkoster@gmail.com> wrote: > Dear all, > > I have a reproducible JVM crash > > The system is Tomcat 6.0.23 with NIO connectors for HTTP and also > relying heavily on NIO to write hundreds of files. I am running with the > G1 garbage collector (-XX:+UseG1GC). More details below. > > My question: what to do now? What information do I need to provide for > someone to fix this problem? How do I get this information? > > Also: should I file a bug report? > > I will re-run using the regular GC to see if this is perhaps G1 related. > > > > [kjkoster@dill ~]$ uname -a > FreeBSD dill.beta-monitor.com 9.0-STABLE FreeBSD 9.0-STABLE #0: Tue Jun > 19 11:46:32 UTC 2012 > root@dill.beta-monitor.com:/usr/obj/usr/src/sys/DILL amd64 > [kjkoster@dill ~]$ /usr/local/openjdk7/bin/java -version > openjdk version "1.7.0_04" > OpenJDK Runtime Environment (build 1.7.0_04-b22) > OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode) > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00000008a6218243, pid=1832, tid=34455804928 > # > # JRE version: 7.0-b22 > # Java VM: OpenJDK 64-Bit Server VM (23.0-b21 mixed mode bsd-amd64 > compressed oops) > # Problematic frame: > # C [libnet.so+0x9243] Java_java_net_SocketInputStream_socketRead0+0xb3 > # > # Failed to write core dump. Core dumps have been disabled. To enable > core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # /lemongrass/lemongrass/lemongrass/hs_err_pid1832.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > > > -- > Kees Jan > > http://java-monitor.com/ > kjkoster@kjkoster.org > +31651838192 > > Change is good. Granted, it is good in retrospect, but change is good. > > _______________________________________________ > freebsd-java@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-java > To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wf6z50q68527sy>