java.lang.IllegalArgumentException: can't parse argument number:

Atlassian JIRA | Joshua Tjhin | 3 years ago
  1. 0

    If you try executing the following code with jul-to-slf4j you get a NumberFormatException, whereas with java.util.logging you get a normal logged message. I.e.: Logger.getLogger("test").log(Level.INFO, "abcd {18=false} {0}", "test"); Result with java.util.logging: Nov 06, 2015 12:42:03 PM Main main INFORMAÇÕES: abcd {18=false} {0} Result with jul-to-slf4j: java.lang.IllegalArgumentException: can't parse argument number: 18=false at java.text.MessageFormat.makeFormat(MessageFormat.java:1420) at java.text.MessageFormat.applyPattern(MessageFormat.java:479) at java.text.MessageFormat.<init>(MessageFormat.java:363) at java.text.MessageFormat.format(MessageFormat.java:835) at org.slf4j.bridge.SLF4JBridgeHandler.getMessageI18N(SLF4JBridgeHandler.java:264) at org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:220) at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:297) at java.util.logging.Logger.log(Logger.java:616) at java.util.logging.Logger.doLog(Logger.java:641) at java.util.logging.Logger.log(Logger.java:685) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.parseInt(Integer.java:527) at java.text.MessageFormat.makeFormat(MessageFormat.java:1418) at java.text.MessageFormat.applyPattern(MessageFormat.java:479) at java.text.MessageFormat.<init>(MessageFormat.java:363) at java.text.MessageFormat.format(MessageFormat.java:835) at org.slf4j.bridge.SLF4JBridgeHandler.getMessageI18N(SLF4JBridgeHandler.java:264) at org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:220) at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:297) org/slf4j/bridge/SLF4JBridgeHandler.java:140 Seems to use MessageFormat directly to parse parameters. But java.util.logging uses java.util.logging.SimpleFormatter for a different handling of parameters.

    QOS.ch JIRA | 1 year ago | Rodolfo Udo Labsch
    java.lang.IllegalArgumentException: can't parse argument number: 18=false
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

  3. 0

    If you try executing the following code with jul-to-slf4j you get a NumberFormatException, whereas with java.util.logging you get a normal logged message. I.e.: Logger.getLogger("test").log(Level.INFO, "abcd {18=false} {0}", "test"); Result with java.util.logging: Nov 06, 2015 12:42:03 PM Main main INFORMAÇÕES: abcd {18=false} {0} Result with jul-to-slf4j: java.lang.IllegalArgumentException: can't parse argument number: 18=false at java.text.MessageFormat.makeFormat(MessageFormat.java:1420) at java.text.MessageFormat.applyPattern(MessageFormat.java:479) at java.text.MessageFormat.<init>(MessageFormat.java:363) at java.text.MessageFormat.format(MessageFormat.java:835) at org.slf4j.bridge.SLF4JBridgeHandler.getMessageI18N(SLF4JBridgeHandler.java:264) at org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:220) at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:297) at java.util.logging.Logger.log(Logger.java:616) at java.util.logging.Logger.doLog(Logger.java:641) at java.util.logging.Logger.log(Logger.java:685) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.parseInt(Integer.java:527) at java.text.MessageFormat.makeFormat(MessageFormat.java:1418) at java.text.MessageFormat.applyPattern(MessageFormat.java:479) at java.text.MessageFormat.<init>(MessageFormat.java:363) at java.text.MessageFormat.format(MessageFormat.java:835) at org.slf4j.bridge.SLF4JBridgeHandler.getMessageI18N(SLF4JBridgeHandler.java:264) at org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:220) at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:297) org/slf4j/bridge/SLF4JBridgeHandler.java:140 Seems to use MessageFormat directly to parse parameters. But java.util.logging uses java.util.logging.SimpleFormatter for a different handling of parameters.

    QOS.ch JIRA | 1 year ago | Rodolfo Udo Labsch
    java.lang.IllegalArgumentException: can't parse argument number: 18=false
  4. 0

    [SLF4J-337] jul-to-slf4j inconsistent message format - QOS.ch JIRA

    qos.ch | 3 months ago
    java.lang.IllegalArgumentException: can't parse argument number: 18=false

  1. Handemelindo 1 times, last 1 week ago
7 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.lang.IllegalArgumentException

    can't parse argument number:

    at java.text.MessageFormat.makeFormat()
  2. Java RT
    MessageFormat.format
    1. java.text.MessageFormat.makeFormat(MessageFormat.java:1420)[na:1.7.0_07]
    2. java.text.MessageFormat.applyPattern(MessageFormat.java:479)[na:1.7.0_07]
    3. java.text.MessageFormat.<init>(MessageFormat.java:363)[na:1.7.0_07]
    4. java.text.MessageFormat.format(MessageFormat.java:835)[na:1.7.0_07]
    4 frames
  3. com.atlassian.stash
    ActiveObjectsRestoreStep.run
    1. com.atlassian.stash.internal.i18n.PluginI18nService.getText(PluginI18nService.java:94)[stash-service-impl-2.8.2.jar:na]
    2. com.atlassian.stash.internal.i18n.PluginI18nService.getText(PluginI18nService.java:85)[stash-service-impl-2.8.2.jar:na]
    3. com.atlassian.stash.internal.i18n.PluginI18nService.getKeyedText(PluginI18nService.java:72)[stash-service-impl-2.8.2.jar:na]
    4. com.atlassian.stash.internal.maintenance.restore.ActiveObjectsRestoreStep.run(ActiveObjectsRestoreStep.java:74)[stash-service-impl-2.8.2.jar:na]
    4 frames