Details
-
Bug
-
Resolution: Done
-
Major
-
7.1.2.Final (EAP)
-
None
-
None
Description
commit 27b56ae78a60f42139d615b289efa32c21aecc69
Author: James Perkins <jperkins@redhat.com>
Date: 2012-04-30 12:59:48 -0700Added translations properties files.
In this commit, Japanese message resource properties are added, but most of them don't specify parameter index properly. We need to rework on these properties files.
For example,
English: "%s is %d"
Japanese: "%d は %s" (Wrong format, this causes parameter format error)
Japanese: "%2$d は %1$s" (Correct format)
In Japanese environment, users cannot read log because it's filled up with bunch of format errors and incorrect logs.
Stack trace from "serverStopped" log:
15:26:28,100 ERROR [stderr] java.util.logging.ErrorManager: 5: Formatting error
15:26:28,100 ERROR [stderr] java.util.IllegalFormatConversionException: d != java.lang.String
15:26:28,101 ERROR [stderr] at java.util.Formatter$FormatSpecifier.failConversion(Formatter.java:3999)
(snip)
15:26:28,106 ERROR [stderr] at org.jboss.logging.Logger.logf(Logger.java:2112)
15:26:28,107 ERROR [stderr] at org.jboss.as.server.ServerLogger_$logger.serverStopped(ServerLogger_$logger.java:114)
15:26:28,107 ERROR [stderr] at org.jboss.as.server.ApplicationServerService.stop(ApplicationServerService.java:182)
Attachments
Issue Links
- relates to
-
AS7-4760 Logging should fallback to English message when format error
- Resolved