Files
2026-03-01 01:43:46 +08:00

2.2 KiB

日期, 来源
日期 来源
2026-01-26 11:24 鹏豪

问题详情

  1. 网关日志记录问题。
  2. IBS 后台为空。(文件过大。)

处理过程

[Host:"p.cdn.10086.cn", X-Forwarded-For:"39.135.1.165, 39.135.122.120", X-From-IP:"39.135.122.120", X-Forwarded-Proto:"http", Connection:"close", 
AccessKey:"d33A76qn", Authorization:"436645554141585231594F724F65304E|68F5E2ED|5583C293D942F17892287BD19F857BE43C09488060D573723419ABEC5EB3BCB5", 
Accept:"*/*", Cache-Control:"no-cache", Pragma:"no-cache", User-Agent:"Java/17.0.6"]

[Host:"p.cdn.10086.cn", X-Forwarded-For:"117.134.3.178, 39.135.122.120", X-From-IP:"39.135.122.120", X-Forwarded-Proto:"http", Connection:"close", User-Agent:"PostmanRuntime/7.29.2", 
Accept:"*/*", 
Postman-Token:"0eee5cff-afbf-4a81-9816-f8f7f703c901", 
Accept-Encoding:"gzip, deflate, br"]

总结

2025-12-22 01:40:02 [fc8dca8800604752] [fc8dca8800604752] [] [portal-117] [http-nio-8080-exec-687] ERROR com.cmcc.cdn.platform.selfservice.service.impl.HttpFileServiceImpl 287 exportAndSaveFileContent - 文件信息保存到数据库失败could not execute statement; nested exception is org.hibernate.exception.GenericJDBCException: could not execute statement org.springframework.orm.jpa.JpaSystemException: could not execute statement; nested exception is org.hibernate.exception.GenericJDBCException: could not execute statement
	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:331) ~[spring-orm-5.3.28.jar!/:5.3.28]
	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:233) ~[spring-orm-5.3.28.jar!/:5.3.28]
	at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.translateExceptionIfPossible(AbstractEntityManagerFactoryBean.java:551) ~[spring-orm-5.3.28.jar!/:5.3.28]
	at org.springframework.dao.support.ChainedPersistenceExceptionTranslator.translateExceptionIfPossible(ChainedPersistenceExceptionTranslator.java:61) ~[spring-tx-5.3.28.jar!/:5.3.28]

数据库限制

Caused by: com.mysql.cj.jdbc.exceptions.PacketTooBigException: Packet for query is too large (25,299,600 > 16,777,216). You can change this value on the server by setting the 'max_allowed_packet' variable.