Date: Wed, 12 May 2010 10:50:40 +0300 From: Achilleas Mantzios <achill@matrix.gatewaynet.com> To: freebsd-java@freebsd.org Subject: Re: openjdk6 crashes Message-ID: <201005121050.41217.achill@matrix.gatewaynet.com> In-Reply-To: <4BE9B02E.2010103@gmail.com> References: <4BE11114.5030306@gmail.com> <201005101246.22215.achill@matrix.gatewaynet.com> <4BE9B02E.2010103@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tuesday 11 May 2010 22:29:50 / Peter Palmreuther : > Am 10.05.10 11:46, schrieb Achilleas Mantzios: > > Στις Saturday 08 May 2010 00:21:02 ο/η Peter Palmreuther έγραψε: > > The program causing the panic was periodic daily. > > For some reason, the same script on the same hardware with the previous 6.2 kernel was working ok. > > *hmmm* OK. I have updated to OpenJDK some time after updating to FreeBSD8. Bot > on the other hand my 'assertion' theory still stands: it's there for a defined > (ugly in consequences but defined!) "way out" and the JVM "goes out" at > exactly this 'assert'-statement. I still see a software related problem more > probable than defect hardware :-) > > > Anyway > > Have your tried > > - native jdk > > Nope. Hesitated to compile this one as well. So much work :-/ Guess I'll go > through it and test it. > > > - the binary diablo > > Not the binary, but a self compiled one. Works. For this issue. But I had > other issues with it in the past and got the advice to use 'openjdk' as it's > actively maintained (in opposite to diablo-jdk). Am I wrong? ???? Diablo is binary by definition, what do you mean by "self compiled"? > > > - the linux jdk with linuxolator > > WTF? Should I really install and activate a linux emulation layer to get a > stable running JRE/JDK? Is this advice just for making sure "other JVMs don't > have this problem" or meant to be a "how to serve JVM on FreeBSD8" advice??? 1st, to set up linux emulation is 30 seconds work. 2nd, it will not be a stable running JRE 3rd, if you feel so insecure with FreeBSD, then some linux distro maybe could save you some further frustrations. There is nobody here who can help, obviously. You may do any combination of the below: - submit a PR - See here: http://openjdk.java.net/projects/bsd-port/ - try the same openjdk version on linux or OSX, to break down the problem. - if you feel hacker enough, try to solve the problem by yourself and submit a patch - contact the people who made the port. (apparently they dont read this list) -- Achilleas Mantzios
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201005121050.41217.achill>