From owner-freebsd-java@FreeBSD.ORG Sun Jul 29 22:50:04 2007 Return-Path: Delivered-To: java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02AF116A419 for ; Sun, 29 Jul 2007 22:50:04 +0000 (UTC) (envelope-from freebsd@spatula.net) Received: from turing.morons.org (turing.morons.org [208.96.51.42]) by mx1.freebsd.org (Postfix) with ESMTP id EA39F13C458 for ; Sun, 29 Jul 2007 22:50:01 +0000 (UTC) (envelope-from freebsd@spatula.net) Received: by turing.morons.org (Postfix, from userid 1001) id 88B0717034; Sun, 29 Jul 2007 15:49:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by turing.morons.org (Postfix) with ESMTP id 49ABE17033 for ; Sun, 29 Jul 2007 15:49:59 -0700 (PDT) Date: Sun, 29 Jul 2007 15:49:59 -0700 (PDT) From: Nick Johnson X-X-Sender: spatula@turing To: java@freebsd.org In-Reply-To: <20070729123750.C82369@turing> Message-ID: <20070729154135.U82369@turing> References: <20070729123750.C82369@turing> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Subject: Re: SAX problems with server VM with patchset 6 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jul 2007 22:50:04 -0000 Recompiling the JDK with gcc 3.4.6 made the problem go away. I guess the moral of the story is if you see strange behaviour from one VM or the other, and you've compiled with gcc 4.2, that might be the reason why... and you may need a recompile with gcc 3.4. Unfortunately I lack the technical knowledge of gcc and the jvm to even begin to speculate as to why this particular problem appeared. It could also just be some bizarre fluke of the way the compile went the first time and any recompile may have similarly resolved the problem. I am not, however, particularly inclined to burn another 2:11:14 compiling again to test this hypothesis. On Sun, 29 Jul 2007, Nick Johnson wrote: > Having problems with SAX in Tigris on FreeBSD 6.2 using the server VM with > Tomcat 6. > > If I specify JAVA_OPTS="-server" in catalina.sh, I get a lot of this > during server startup: > > org.xml.sax.SAXParseException: Attribute "null" was already specified for element "null". > > (Consequently Tomcat can't process the server.xml configuration file and > promptly dies.) > > If I don't specify -server, it starts up fine with no parsing problems. > > The -server option doesn't seem to give trouble with the Windows 1.5.0_12 > VM, so I suspect this is a VM bug with Tigris. > > As I built the JDK with GCC 4.2.1, and used 3.x in the past, I'm going to > try compiling with 3.x to see if that makes any difference. I'll post the > results after that is done. > > Nick > > -- "Courage isn't just a matter of not being frightened, you know. It's being afraid and doing what you have to do anyway." Doctor Who - Planet of the Daleks This message has been brought to you by Nick Johnson 2.3b1 and the number 6. http://healerNick.com/ http://morons.org/ http://spatula.net/