failed to parse [priority]

Samebug tips2

Java does not handle IPv6 nameservers before 1.8.0_60. Upgrade to the latest JVM.

This is a bug in Wise, updating to v4.10 seems to solve the problem.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web265

  • via JIRA by Boy van Duuren, 1 year ago
    failed to parse [priority]
  • via JIRA by Boy van Duuren, 1 year ago
    failed to parse [priority]
  • failed to parse [priority]
  • Stack trace

    • org.elasticsearch.index.mapper.MapperParsingException: failed to parse [priority] at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse( at org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue( at org.elasticsearch.index.mapper.object.ObjectMapper.parse( at org.elasticsearch.index.mapper.DocumentMapper.parse( at org.elasticsearch.index.mapper.DocumentMapper.parse( at org.elasticsearch.index.shard.IndexShard.prepareCreate( at org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation( at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary( at$PrimaryPhase.performOnPrimary( at$PrimaryPhase$1.doRun( at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: java.lang.NumberFormatException: For input string: "DEBUG" at java.lang.NumberFormatException.forInputString( at java.lang.Long.parseLong( at java.lang.Long.parseLong( at at org.elasticsearch.index.mapper.core.LongFieldMapper.innerParseCreateField( at org.elasticsearch.index.mapper.core.NumberFieldMapper.parseCreateField( at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse( ... 13 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    2 times, 2 weeks ago
    2 times, 2 months ago
    Once, 2 months ago
    Once, 5 months ago
    Once, 9 months ago
    207 more bugmates