From owner-freebsd-java@FreeBSD.ORG Sun Apr 4 15:08:36 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 1D12F16A4CE for ; Sun, 4 Apr 2004 15:08:36 -0700 (PDT) Received: from fielden.com.au (www.fielden.com.au [203.34.58.131]) by mx1.FreeBSD.org (Postfix) with SMTP id 95BEE43D55 for ; Sun, 4 Apr 2004 15:08:31 -0700 (PDT) (envelope-from david@fielden.com.au) Received: (qmail 5899 invoked from network); 4 Apr 2004 22:08:25 -0000 Received: from unknown (HELO fielden.com.au) (192.168.1.84) by persephone.fielden.com.au with SMTP; 4 Apr 2004 22:08:25 -0000 Message-ID: <40708758.3050700@fielden.com.au> Date: Mon, 05 Apr 2004 08:08:24 +1000 From: Rowdy User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-java@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 5.1, Tomcat 5.0.19, which JDK? 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: Sun, 04 Apr 2004 22:08:36 -0000 Greetings, I hav been trying to get Tomcat to run on my FBSD 5.1-R system, but have been experiencing the infamous: SIGBUS 10* bus error Full thread dump Classic VM (diablo-1.3.1-0, green threads): ... A (partial) portversion output from my system (hopefully including all that is relevant) is: diablo-jdk-1.3.1.0_1 = up-to-date with port jakarta-tomcat-5.0.19 = up-to-date with port javavmwrapper-1.4 = up-to-date with port jdk-1.4.2p6_4 = up-to-date with port linux-sun-jdk-1.4.2.04 = up-to-date with port linux_base-7.1_7 = up-to-date with port A quick Google revealed that the solution for nearly everyone else with the same error was to upgrade something (OS version, Tomcat, Diablo etc.), however everything here is up to date, the server is cvsuped regularly. I wondered whether it was an issue with the Diablo JDK, but I couldn't find an easy way of changing it, especially when the path to diablo/bin appears to be hard-wired into tomcat50ctl. I renamed the diablo directory and made a symlink from the jdk-1.4.2 directory to the diablo-1.3.1 directory, and restarted tomcat. To my surprise it started just fine. I ran thru a few of the examples, left tomcat it running overnight, and the next morning (and, in fact, the morning after that too) it was still running. So the question probably is: does Tomcat 5 really *need* the Diablo JDK or will it run fine with the other one? Btw this is not a production server, just something for me to play with at home, so high-availbility is not required, but the less maintenance the better :) Thanx Dave