From owner-freebsd-java@FreeBSD.ORG Mon Dec 13 16:48:41 2004 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5AC816A4CE for ; Mon, 13 Dec 2004 16:48:41 +0000 (GMT) Received: from gollum.cambrium.nl (mx1.cambrium.nl [217.19.16.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 017EF43D49 for ; Mon, 13 Dec 2004 16:48:41 +0000 (GMT) (envelope-from j.verschoor@nefli.nl) Received: (qmail 29732 invoked from network); 13 Dec 2004 16:48:40 -0000 Received: from 217-19-20-68.dsl.cambrium.nl (HELO ?192.168.1.142?) (217.19.20.68) by gollum.cambrium.nl with SMTP; 13 Dec 2004 16:48:40 -0000 Message-ID: <41BDC7F6.2090900@nefli.nl> Date: Mon, 13 Dec 2004 17:48:54 +0100 From: Joris Verschoor Organization: Nefli B.V. User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-java@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 5.3-RELEASE + JDK1.4 native in a Jail -> hangs 99% cpu on kserel X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2004 16:48:41 -0000 Achilleus Mantzios wrote: >Just some thoughts: > >- Postgresql unfortunately cant be jailified since IPC is not >meant to be jailified itself. >(BTW have you set security.jail.sysvipc_allowed=1 ??) > > Yep I've set that >Hmm. native,green,classic is not an option anymore. >Only -client,-server (hotspot). > > right.. > >Always have an eye on the postgresql log. >Maybe the backend was non gracefully restarted due to a >jail IPC failure. >What does the postgresql log say? > > I've only some constraint errors when I do something wrong myself :) >Which postgresql are you running? >I suggest 7.4.6 (the lastest stable). > > I'm running 7.4.6 >Also make sure the jdbc driver in in sync >with your backend. > > pg74.215.jdbc3.jar >Also... an advice: Dont use the ports for postgresql. >Manually manage your installations, because even for >minor releases updates you could do a real harm to your >database if you rely on the ports/packages upgrade mechanisms. > > When I upgrade, I always use pg_dump to backup dbs >No script will ever do : > >UPDATE pg_type where oid=... ; > >kinds of things. > > I'm doing only user table queries..