spring boot 当参数传入开头多个0时，报错：JSON parse error: Invalid numeric value: Leading zeroes not allowed...

最新推荐文章于 2023-12-20 14:00:24 发布
转载 最新推荐文章于 2023-12-20 14:00:24 发布 · 1.4k 阅读 · 1 ·
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/wang-yaz/p/10532761.html
文章标签：

#json #java

本文介绍了解决Jackson在解析JSON配置时遇到的数值前导零问题的方法。通过在配置文件中设置spring.jackson.parser.allow-numeric-leading-zeros=true，可以有效避免因前导零导致的解析错误。
Wan2.2-T2V-A5B

Wan2.2-T2V-A5B

文生视频
Wan2.2

Wan2.2是由通义万相开源高效文本到视频生成模型，是有​50亿参数的轻量级视频生成模型，专为快速内容创作优化。支持480P视频生成，具备优秀的时序连贯性和运动推理能力

原因是：

Jackson解析json配置的问题

在配置文件中设置下：

spring.jackson.parser.allow-numeric-leading-zeros=true

 

转载于:https://www.cnblogs.com/wang-yaz/p/10532761.html

您可能感兴趣的与本文相关的镜像

Wan2.2-T2V-A5B

Wan2.2-T2V-A5B

文生视频
Wan2.2

Wan2.2是由通义万相开源高效文本到视频生成模型，是有​50亿参数的轻量级视频生成模型，专为快速内容创作优化。支持480P视频生成，具备优秀的时序连贯性和运动推理能力

adviceuser2014
关注
在 Node.js v12.16.2 版本中，`Buffer` 是用于处理二进制数据的核心模块之一
BLOG域名:programb.blog.youkuaiyun.com
04-16 591
在 Node.js v12.16.2 版本中，Buffer是用于处理二进制数据的核心模块之一。它提供了一种机制来创建和操作原始字节序列，这使得开发者可以轻松地读取文件、处理网络流以及执行其他涉及二进制数据的操作。
IDAPython类库---idc.py的源码
墨鱼菜鸡
03-20 941
#!/usr/bin/env python #--------------------------------------------------------------------- # IDAPython - Python plugin for Interactive Disassembler # #...
spring boot 当参数传入开头多个0时，报错：JSON parse error: Invalid numeric value: Leading zeroes not allowed
weixin_44071721的博客
06-10 1356
有可能是jackson解析配置问题 需要确认是否开启了以０开始读取信息 @Configuration public class WebMvcConfig implements WebMvcConfigurer { @Bean public HttpMessageConverter<String> responseBodyConverter(){ StringHttpMessageConverter converter = new StringHttpMessageConverter(Ch
解决Invalid numeric Value:Leading zeroes not allowed问题
qq_55076730的博客
09-25 8698
解决Invalid numeric Value:Leading zeroes not allowed
springboot项目中使用redis对数据进行解析报Invalid numeric value: Leading zeroes not allowed错误
今晚摸鱼
03-23 6668
错误分析 在使用redis获取发送的短信验证码，偶尔会报如下错误信息 2019-01-15 10:32:15.104 [http-nio-8080-exec-10] WARN org.springframework.web.servlet.PageNotFound:1176 - No mapping found f lowed at [Source: [B@2836aebe; line: 1,...
spring boot报错Invalid numeric value: Leading zeroes not allowed
iamlzyoco的博客
06-05 5524
场景：用swagger测试接口时，传递的参数中有0开头的，如下： 接口返回结果报错：Invalid numeric value: Leading zeroes not allowed 解决方案：在application.yml中，加上 spring.jackson.parser.allow-numeric-leading-zeros：true 即可。 ...
Invalid numeric value: Leading zeroes not allowed
最新发布
06-18
在Spring Boot项目中，当请求参数存在以0开头的正整数时，可能会触发`JSON parse error: Invalid numeric value: Leading zeroes not allowed`错误。这是由于JSON标准不允许数值以非零开头[^1]。 为了处理这个问题...
[root@localhost snort-2.9.20]# sudo /usr/share/logstash/bin/logstash -f /etc/logstash/conf.d/snort-logstash.conf Using bundled JDK: /usr/share/logstash/jdk OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. WARNING: Could not find logstash.yml which is typically located in $LS_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults Could not find log4j2 configuration at path /usr/share/logstash/config/log4j2.properties. Using default config which logs errors to the console [INFO ] 2025-05-16 11:06:04.632 [main] runner - Starting Logstash {"logstash.version"=>"7.17.28", "jruby.version"=>"jruby 9.2.20.1 (2.5.8) 2021-11-30 2a2962fbd1 OpenJDK 64-Bit Server VM 11.0.26+4 on 11.0.26+4 +indy +jit [linux-x86_64]"} [INFO ] 2025-05-16 11:06:04.636 [main] runner - JVM bootstrap flags: [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djdk.io.File.enableADS=true, -Djruby.compile.invokedynamic=true, -Djruby.jit.threshold=0, -Djruby.regexp.interruptible=true, -XX:+HeapDumpOnOutOfMemoryError, -Djava.security.egd=file:/dev/urandom, -Dlog4j2.isThreadContextMapInheritable=true] [WARN ] 2025-05-16 11:06:04.817 [LogStash::Runner] multilocal - Ignoring the 'pipelines.yml' file because modules or command line options are specified [INFO ] 2025-05-16 11:06:05.485 [Api Webserver] agent - Successfully started Logstash API endpoint {:port=>9601, :ssl_enabled=>false} [INFO ] 2025-05-16 11:06:06.392 [Converge PipelineAction::Create<main>] Reflections - Reflections took 43 ms to scan 1 urls, producing 119 keys and 419 values [WARN ] 2025-05-16 11:06:06.920 [Converge PipelineAction::Create<main>] json - Relying on default value of `pipeline.ecs_compatibility`, which may change in a future major release of Logstash. To avoid unexpected changes when upgrading Logstash, please explicitly declare your desired ECS Compatibility mode. [WARN ] 2025-05-16 11:06:06.957 [Converge PipelineAction::Create<main>] file - Relying on default value of `pipeline.ecs_compatibility`, which may change in a future major release of Logstash. To avoid unexpected changes when upgrading Logstash, please explicitly declare your desired ECS Compatibility mode. [WARN ] 2025-05-16 11:06:07.101 [Converge PipelineAction::Create<main>] plain - Relying on default value of `pipeline.ecs_compatibility`, which may change in a future major release of Logstash. To avoid unexpected changes when upgrading Logstash, please explicitly declare your desired ECS Compatibility mode. [WARN ] 2025-05-16 11:06:07.125 [Converge PipelineAction::Create<main>] elasticsearch - Relying on default value of `pipeline.ecs_compatibility`, which may change in a future major release of Logstash. To avoid unexpected changes when upgrading Logstash, please explicitly declare your desired ECS Compatibility mode. [INFO ] 2025-05-16 11:06:07.257 [[main]-pipeline-manager] elasticsearch - New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["http://localhost:9200"]} [INFO ] 2025-05-16 11:06:07.459 [[main]-pipeline-manager] elasticsearch - Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://localhost:9200/]}} [WARN ] 2025-05-16 11:06:07.601 [[main]-pipeline-manager] elasticsearch - Restored connection to ES instance {:url=>"http://localhost:9200/"} [INFO ] 2025-05-16 11:06:07.610 [[main]-pipeline-manager] elasticsearch - Elasticsearch version determined (7.17.28) {:es_version=>7} [WARN ] 2025-05-16 11:06:07.611 [[main]-pipeline-manager] elasticsearch - Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type {:es_version=>7} [INFO ] 2025-05-16 11:06:07.649 [Ruby-0-Thread-10: :1] elasticsearch - Config is not compliant with data streams. `data_stream => auto` resolved to `false` [INFO ] 2025-05-16 11:06:07.650 [[main]-pipeline-manager] elasticsearch - Config is not compliant with data streams. `data_stream => auto` resolved to `false` [WARN ] 2025-05-16 11:06:07.654 [[main]-pipeline-manager] json - Relying on default value of `pipeline.ecs_compatibility`, which may change in a future major release of Logstash. To avoid unexpected changes when upgrading Logstash, please explicitly declare your desired ECS Compatibility mode. [WARN ] 2025-05-16 11:06:07.661 [[main]-pipeline-manager] grok - Relying on default value of `pipeline.ecs_compatibility`, which may change in a future major release of Logstash. To avoid unexpected changes when upgrading Logstash, please explicitly declare your desired ECS Compatibility mode. [INFO ] 2025-05-16 11:06:07.683 [Ruby-0-Thread-10: :1] elasticsearch - Using a default mapping template {:es_version=>7, :ecs_compatibility=>:disabled} [INFO ] 2025-05-16 11:06:07.806 [[main]-pipeline-manager] javapipeline - Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>500, "pipeline.sources"=>["/etc/logstash/conf.d/snort-logstash.conf"], :thread=>"#<Thread:0x5d6da427 run>"} [INFO ] 2025-05-16 11:06:08.357 [[main]-pipeline-manager] javapipeline - Pipeline Java execution initialization time {"seconds"=>0.55} [INFO ] 2025-05-16 11:06:08.388 [[main]-pipeline-manager] javapipeline - Pipeline started {"pipeline.id"=>"main"} [INFO ] 2025-05-16 11:06:08.413 [[main]<file] observingtail - START, creating Discoverer, Watch with file and sincedb collections [INFO ] 2025-05-16 11:06:08.417 [Agent thread] agent - Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]} [WARN ] 2025-05-16 11:06:08.560 [[main]<file] json - Relying on default value of `pipeline.ecs_compatibility`, which may change in a future major release of Logstash. To avoid unexpected changes when upgrading Logstash, please explicitly declare your desired ECS Compatibility mode. [ERROR] 2025-05-16 11:06:08.594 [[main]<file] json - JSON parse error, original data now in message field {:message=>"Unexpected character ('*' (code 42)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')\n at [Source: (String)\"[**] [1:1000001:1] HTTP Traffic Detected [**]\"; line: 1, column: 3]", :exception=>LogStash::Json::ParserError, :data=>"[**] [1:1000001:1] HTTP Traffic Detected [**]"} [ERROR] 2025-05-16 11:06:08.613 [[main]<file] json - JSON parse error, original data now in message field {:message=>"Unrecognized token 'Priority': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')\n at [Source: (String)\"[Priority: 0] \"; line: 1, column: 10]", :exception=>LogStash::Json::ParserError, :data=>"[Priority: 0] "} [ERROR] 2025-05-16 11:06:08.615 [[main]<file] json - JSON parse error, original data now in message field {:message=>"Invalid numeric value: Leading zeroes not allowed\n at [Source: (String)\"05/12-11:19:15.076019 192.168.208.17:56626 -> 128.112.18.21:80\"; line: 1, column: 2]", :exception=>LogStash::Json::ParserError, :data=>"05/12-11:19:15.076019 192.168.208.17:56626 -> 128.112.18.21:80"} [ERROR] 2025-05-16 11:06:08.616 [[main]<file] json - JSON parse error, original data now in message field {:message=>"Unrecognized token 'TCP': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')\n at [Source: (String)\"TCP TTL:64 TOS:0x0 ID:15629 IpLen:20 DgmLen:40 DF\"; line: 1, column: 4]", :exception=>LogStash::Json::ParserError, :data=>"TCP TTL:64 TOS:0x0 ID:15629 IpLen:20 DgmLen:40 DF"} [ERROR] 2025-05-16 11:06:08.616 [[main]<file] json - JSON parse error, original data now in message field {:message=>"Unexpected character ('*' (code 42)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')\n at [Source: (String)\"***A**** Seq: 0xEFEA3D49 Ack: 0x16551DAE Win: 0x7210 TcpLen: 20\"; line: 1, column: 2]", :exception=>LogStash::Json::ParserError, :data=>"***A**** Seq: 0xEFEA3D49 Ack: 0x16551DAE Win: 0x7210 TcpLen: 20"} [WARN ] 2025-05-16 11:06:08.730 [[main]>worker2] json - Error parsing json {:source=>"message", :raw=>"[**] [1:1000001:1] HTTP Traffic Detected [**]", :exception=>#<LogStash::Json::ParserError: Unexpected character ('*' (code 42)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (byte[])"[**] [1:1000001:1] HTTP Traffic Detected [**]"; line: 1, column: 3]>} { "host" => "localhost.localdomain", "message" => "05/12-11:19:15.076019 192.168.208.17:56626 -> 128.112.18.21:80", "path" => "/var/log/snort/alert", "tags" => [ [0] "_jsonparsefailure", [1] "_grokparsefailure" ] } { "host" => "localhost.localdomain", "message" => "[**] [1:1000001:1] HTTP Traffic Detected [**]", "path" => "/var/log/snort/alert", "tags" => [ [0] "_jsonparsefailure" ] } { "host" => "localhost.localdomain", "message" => "TCP TTL:64 TOS:0x0 ID:15629 IpLen:20 DgmLen:40 DF", "path" => "/var/log/snort/alert", "tags" => [ [0] "_jsonparsefailure", [1] "_grokparsefailure" ] } { "host" => "localhost.localdomain", "priority" => "0", "message" => "[Priority: 0] ", "path" => "/var/log/snort/alert", "tags" => [ [0] "_jsonparsefailure" ] } { "host" => "localhost.localdomain", "message" => "***A**** Seq: 0xEFEA3D49 Ack: 0x16551DAE Win: 0x7210 TcpLen: 20", "path" => "/var/log/snort/alert", "tags" => [ [0] "_jsonparsefailure", [1] "_grokparsefailure" ] }
05-17
[ERROR] 2025-05-16 11:06:08.594 [[main]] json - JSON parse error, original data now in message field {:message=>"Unexpected character ('*' (code 42)): expected a valid value (JSON String, Number, ...
IDA 7.0 python / idc.py
BreakingPoint
04-11 5964
#!/usr/bin/env python #--------------------------------------------------------------------- # IDAPython - Python plugin for Interactive Disassembler # # Original IDC.IDC: # Copyright (c) 1990-2010 Ilf
请求参数存在以0开头的正整数，报JSON parse error：Invalid numeric value：Leading zeroes not allowed错误
热门推荐
正能量炯哥的博客
01-10 1万+
spring boot项目中，请求参数存在以0开头的正整数，报JSON parse error：Invalid numeric value：Leading zeroes not allowed错误，错误提示就是说不允许以0开头   用swagger接口测试的时候传的参数值中有以0开头的正整数     最后的解决方式是添加一个配置类来解决，然后传的参数值05将自动被转换为5存入数据...
JSON parse error: Invalid numeric value: Leading zeroes not allowed
liutianliang9720的博客
01-02 6767
JSON parse error: Invalid numeric value: Leading zeroes not allowed 分享一个小小的错误问题，无意之中踩的坑。近期学习elasticsearch，进行索引数据的添加，用postman调试接口时，发现报了以下的错误。 我百思不得其解，怀疑自己的JSON格式错误格式，去解析一遍JSON格式发现没有问题，于是又回过头来看错误信息，定位到...
spring获取配置文件中的值的问题，比如6个0只获取到一个
z132411的博客
03-27 801
在类中使用@Value注解获取yml配置文件中的值时，需要注意： 1、yml文件中，当值为0000，这种类型的值时，需要用双引号将值引起来。比如： 错误：key=0000 正确：key=“0000” 如果不使用双引号的话，在使用@value注解时，得到的值是0，而不是0000 2、使用@Value注解得到的是null。需要使用@Autowired进行注入，对应类需要加上@Service ...
Minor number must not contain leading zeroes Docker mac
随笔记录-分享&记忆
04-11 1579
Freddy-Shen-MBP:local user$ oc cluster up -- Checking OpenShift client ... OK -- Checking Docker client ... OK -- Checking Docker version ... FAIL    Error: Minor number must not contain leading
jackson解析0开头的纯数字的字符串报错问题浅析
雪落南城的博客
08-03 2564
1、首先提供了修改配置： spring: jackson: parser: allow-numeric-leading-zeros: true 2、最开始没生效 JacksonAutoConfiguration 这个类没有被加工成bean 在启动类上加了包扫描路径 @ComponentScan(basePackages = { "org.springframework.boot.autoconfigure.jackson" }) 配置生效了 3、但是泛化调用的时候还是报错 cau
Spark1.6新特性简介及个人的理解
探索中前进的Rock
01-11 199
新的Spark1.6版本发布了，之前使用Spark1.4版本的SparkSQL，这次发布后主要关注了1.6版本的SparkSQL特性参阅了官方的Release Note和jira issue detail以及之前在使用1.4.0中的经验，跟大家分享一下Spark1.6部分新加的几个特性。   1. Dataset API目前Spark有两大类API:RDD API(Spark Core),D...
Jackson 注解及配置大全
weixin_45817985的博客
12-20 834
Jackson 注解及配置大全
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值