Hi I posted a message some time ago regarding getting JDK 1.3.1_02 running on CentOS4.1 - I mamaged to get this to run by installing the Oracle patch from metalink. A user is now approaching me with an error that has appeared during compilation after going from RedHat7.3 -> CentOS4.1 The error is error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null We HAVE to use JDK 1.3.1_02 for this app (not comething we can change) so does anyone have any suggestions as to what the issue could be? THis JDK does run but something bomb on the compile. thanks for any ideas
> I posted a message some time ago regarding getting JDK 1.3.1_02 running > on CentOS4.1 - I mamaged to get this to run by installing the Oracle > patch from metalink. A user is now approaching me with an error that has > appeared during compilation after going from RedHat7.3 -> CentOS4.1 > > The error is > > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, null > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, null > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, null > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, null > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, null > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, null > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, null > error: compiler message file broken: > key=compiler.err.sun.io.MalformedInputException arguments=null, null, > null, null, null, null, nullit seems within this JVM the language settings are a bit 'off' and they don't know how to interpret the LANG of the environment correctly and so when an exception occurs the JVM blows up trying to generate the exception - Setting the LANG from en_GB.UTF-8 to nothing duing compilation allows this to work. A little strange but a workaround at least for legacy apps