[ARTEMIS-2668] Wrong formatting Strings in class LoggingResultSet

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.11.0
• Fix Version/s: 2.12.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Benjamin Graf
• Created: 19/Mar/20 17:03
• Updated: 16/Apr/20 22:52
• Resolved: 23/Mar/20 20:18

Description

Several methods of LoggingResultSet have wrong amount of parameters in formatting String causing exception if TRACE logging.

e.g.

AMQ222010: Critical IO Error, shutting down the server. file=org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile@27cbabd3, message=Error writing to JDBC file.
java.util.MissingFormatArgumentException: Format specifier '%s'
        at java.util.Formatter.format(Formatter.java:2672) ~[?:?]
        at java.util.Formatter.format(Formatter.java:2609) ~[?:?]
        at java.lang.String.format(String.java:2897) ~[?:?]
        at org.ops4j.pax.logging.jbosslogging.JBossLoggingLogger.doLogf(JBossLoggingLogger.java:87) ~[!/:?]
        at org.jboss.logging.Logger.logf(Logger.java:2326) ~[!/:?]
        at org.apache.activemq.artemis.jdbc.store.logging.LoggingResultSet.updateBlob(LoggingResultSet.java:950) ~[!/:?]

Issue Links

• is a child of: ARTEMIS-975 Reading messages from page causes lost entries in db backend
• links to: GitHub Pull Request #3035