Date: Wed, 12 May 2010 10:26:22 +0200 From: Peter Palmreuther <pitpalme@gmail.com> To: freebsd-java@freebsd.org Subject: Re: openjdk6 crashes Message-ID: <4BEA662E.9040108@gmail.com> In-Reply-To: <201005121050.41217.achill@matrix.gatewaynet.com> References: <4BE11114.5030306@gmail.com> <201005101246.22215.achill@matrix.gatewaynet.com> <4BE9B02E.2010103@gmail.com> <201005121050.41217.achill@matrix.gatewaynet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12.05.10 09:50, Achilleas Mantzios wrote: > Στις 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"? *erm* My fault. Last time I ran 'portupgrade' for 'diablo-jdk16' it did a lot of stuff and I left it running unattended as it seemed to take a while. After all this "openjdk-compiling" stuff I guess I mixed my remembrance about what exactly happened. Additionally I thought you meant "pkgadd -r" or "portupgrade -PP" when asking for "binary diablo". Mea culpa. To make myself clear: I tried diablo the way it comes through port installation; Which in fact seems to be binary. Stupid me. >>> - 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. I wasn't talking about a matter of time, although it took quite longer than 30 seconds to finish portupgrade installing linux_base. I was only wondering if it's "the way to go", activating an emulator, when there is (or should be) native support for one thing (like JVM). > 2nd, it will not be a stable running JRE Thanks. That answered my question, so it's only a validation using linux-jvm > 3rd, if you feel so insecure with FreeBSD, then some linux distro maybe could save you some further frustrations. If I'd feel insecure with FreeBSD I wouldn't have switched to it coming from Debian. And I can't see the point in my post implying I feel insecure on FreeBSD. I only wondered about the "emulation thing" and if I got something completely wrong. What I've read, seen and experienced about FreeBSD wasn't "let's emulate if it's already somewhere else", it was more: "If we need it, it should run natively, stable, open and quiet (enough)!". Sure, it's not "pure fun" not being able to run the Nexus Index updates right now, but all I'm looking for is find a way it works rock solid again. There's no frustration (yet) and I know there's no bug free software. And although I still have to get used to FreeBSD much more (I'm tainted with Linux, so I still figure the differences in handling the system) I'm quite happy with it. It (usually) "just works". > 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) Thanks. The last point was one thing I was hoping for. Port-Maintainers of 'openjdk' being somehow subscribed to 'freebsd-java'. I'll try the other ports as well as soon as I get the time and than follow your advices and most probably open a PR. -- Thanks and best regards, Peter Palmreuther
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BEA662E.9040108>