SAX problems with server VM with patchset 6

[Nick Johnson]

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/