Date: Thu, 6 May 2010 10:12:14 +1000 From: Antony Mawer <lists@mawer.org> To: Peter Palmreuther <pitpalme+unix@gmail.com> Cc: freebsd-java@freebsd.org Subject: Re: openjdk6 crashes Message-ID: <r2tea2d4a5b1005051712ya7772579pa659a1337dcd708c@mail.gmail.com> In-Reply-To: <4BE1D7BF.70605@gmail.com> References: <4BE11114.5030306@gmail.com> <h2lbe800d231005050915lc8dc5973jcbf65ceee931b06d@mail.gmail.com> <4BE1D7BF.70605@gmail.com>
index | next in thread | previous in thread | raw e-mail
On Thu, May 6, 2010 at 6:40 AM, Peter Palmreuther <pitpalme+unix@gmail.com> wrote: > On 05.05.10 18:15, Nicklas Johnson wrote: >> I see this comment near the assert: >> >> // Make sure the stack has at least enough depth to execute >> // the current bytecode. >> >> So possibly increasing the stack size could help? Try -Xss2m or >> -Xss4m. Though this could also be referring to an internal compiler >> stack and have nothing to do with the Java thread stack, so it may not >> matter at all. Something that's easy to try at least. > > Tried and failed. See attached 'hs_err_pid83265.log'. Seems it's (as somehow > expected) the compiler stack, not the "normal" Java Stack?!? > > Anybody or anything else? > > I'd really like to have a mostly stable JRE/JDK running on my FreeBSD. Diablo > I was recommended to replace by OpenJDK, because it's not gonna be that > actively maintained OpenJDK is ... > > So what options exist for a stable up-to-date JDK6@FreeBSD8? I was running Tomcat under OpenJDK6 on FreeBSD 8.0/amd64, but experienced numerous difficulties with PDF generation using the iText library. The same setup running on a Linux system worked OK, and swapping OpenJDK out for Diablo also resolved the problems, so I wonder if there is still some things missing from the OpenJDK port that are included with Diablo...? --Antonyhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?r2tea2d4a5b1005051712ya7772579pa659a1337dcd708c>