. ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v3.3.2-SNAPSHOT) 2025-12-09T09:37:50.082Z INFO 312252 --- [ main] c.i.d.DgttCheckDocApiApplicationKt : Starting DgttCheckDocApiApplicationKt v0.0.1-SNAPSHOT using Java 21.0.9 with PID 312252 (/var/www/html/dgttcheckdocapi/dgttCheckDocApi-0.0.1-SNAPSHOT.jar started by initialdev in /var/www/html/dgttcheckdocapi) 2025-12-09T09:37:50.086Z INFO 312252 --- [ main] c.i.d.DgttCheckDocApiApplicationKt : No active profile set, falling back to 1 default profile: "default" 2025-12-09T09:37:51.478Z INFO 312252 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode. 2025-12-09T09:37:51.543Z INFO 312252 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 57 ms. Found 3 JPA repository interfaces. 2025-12-09T09:37:52.267Z INFO 312252 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port 9090 (http) 2025-12-09T09:37:52.302Z INFO 312252 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2025-12-09T09:37:52.302Z INFO 312252 --- [ main] o.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/10.1.26] 2025-12-09T09:37:52.352Z INFO 312252 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2025-12-09T09:37:52.353Z INFO 312252 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 2130 ms 2025-12-09T09:37:52.530Z INFO 312252 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default] 2025-12-09T09:37:52.625Z INFO 312252 --- [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 6.5.2.Final 2025-12-09T09:37:52.668Z INFO 312252 --- [ main] o.h.c.internal.RegionFactoryInitiator : HHH000026: Second-level cache disabled 2025-12-09T09:37:53.087Z INFO 312252 --- [ main] o.s.o.j.p.SpringPersistenceUnitInfo : No LoadTimeWeaver setup: ignoring JPA class transformer 2025-12-09T09:37:53.128Z INFO 312252 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting... 2025-12-09T09:37:53.603Z INFO 312252 --- [ main] com.zaxxer.hikari.pool.HikariPool : HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@5788722f 2025-12-09T09:37:53.605Z INFO 312252 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed. 2025-12-09T09:37:53.679Z WARN 312252 --- [ main] org.hibernate.orm.deprecation : HHH90000025: MySQLDialect does not need to be specified explicitly using 'hibernate.dialect' (remove the property setting and it will be selected by default) 2025-12-09T09:37:54.699Z INFO 312252 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000489: No JTA platform available (set 'hibernate.transaction.jta.platform' to enable JTA platform integration) Hibernate: alter table documents modify column additional_info json 2025-12-09T09:37:54.973Z INFO 312252 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' 2025-12-09T09:37:55.799Z INFO 312252 --- [ main] eAuthenticationProviderManagerConfigurer : Global AuthenticationManager configured with AuthenticationProvider bean with name authenticationProvider 2025-12-09T09:37:55.800Z WARN 312252 --- [ main] r$InitializeUserDetailsManagerConfigurer : Global AuthenticationManager configured with an AuthenticationProvider bean. UserDetailsService beans will not be used for username/password login. Consider removing the AuthenticationProvider bean. Alternatively, consider using the UserDetailsService in a manually instantiated DaoAuthenticationProvider. 2025-12-09T09:37:55.870Z WARN 312252 --- [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning 2025-12-09T09:37:56.695Z INFO 312252 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port 9090 (http) with context path '/' 2025-12-09T09:37:56.719Z INFO 312252 --- [ main] c.i.d.DgttCheckDocApiApplicationKt : Started DgttCheckDocApiApplicationKt in 7.144 seconds (process running for 7.951) 2025-12-09T09:46:46.415Z INFO 312252 --- [nio-9090-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet 'dispatcherServlet' 2025-12-09T09:46:46.416Z INFO 312252 --- [nio-9090-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet' 2025-12-09T09:46:46.417Z INFO 312252 --- [nio-9090-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 1 ms Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 where d1_0.identification_number=? Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 where d1_0.identification_number=? Message envoyé avec succès : com.google.firebase.messaging.BatchResponseImpl@50c40f5a Hibernate: insert into report_events (document_identifier,document_status,document_type,is_approved,latitude,longitude,scanned_at,scanned_by) values (?,?,?,?,?,?,?,?) Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 where d1_0.identification_number=? Hibernate: select res1_0.id,res1_0.document_identifier,res1_0.document_status,res1_0.document_type,res1_0.is_approved,res1_0.latitude,res1_0.longitude,res1_0.scanned_at,res1_0.scanned_by from report_events res1_0 Hibernate: select res1_0.id,res1_0.document_identifier,res1_0.document_status,res1_0.document_type,res1_0.is_approved,res1_0.latitude,res1_0.longitude,res1_0.scanned_at,res1_0.scanned_by from report_events res1_0 Hibernate: select res1_0.id,res1_0.document_identifier,res1_0.document_status,res1_0.document_type,res1_0.is_approved,res1_0.latitude,res1_0.longitude,res1_0.scanned_at,res1_0.scanned_by from report_events res1_0 2025-12-09T13:29:20.020Z INFO 312252 --- [nio-9090-exec-1] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x000xee0x010x000x000xea0x030x03r0xd39tC0x1bN0x89ED70xf10xa50xd420xa3:0x9b0x080x890xeb0xc8e0xd40xf70x040xe10xc10x980xf40xf00xe5 ]. HTTP method names must be tokens at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:407) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:262) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:904) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) ~[tomcat-embed-core-10.1.26.jar!/:na] at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na] Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 2025-12-10T14:09:07.284Z INFO 312252 --- [nio-9090-exec-6] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x000xee0x010x000x000xea0x030x03p0xa8sL0x910xf20xb50xf6k0x940xb9GV0xf00xb4m0xf60xe00xaf0xa90xed0x090xc00xbcz0xc20x07v0xbc0x0e7F ]. HTTP method names must be tokens at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:407) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:262) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:904) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) ~[tomcat-embed-core-10.1.26.jar!/:na] at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na] Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 Hibernate: select res1_0.id,res1_0.document_identifier,res1_0.document_status,res1_0.document_type,res1_0.is_approved,res1_0.latitude,res1_0.longitude,res1_0.scanned_at,res1_0.scanned_by from report_events res1_0 Hibernate: select res1_0.id,res1_0.document_identifier,res1_0.document_status,res1_0.document_type,res1_0.is_approved,res1_0.latitude,res1_0.longitude,res1_0.scanned_at,res1_0.scanned_by from report_events res1_0 Hibernate: select res1_0.id,res1_0.document_identifier,res1_0.document_status,res1_0.document_type,res1_0.is_approved,res1_0.latitude,res1_0.longitude,res1_0.scanned_at,res1_0.scanned_by from report_events res1_0 Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 where d1_0.identification_number=? Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 where d1_0.identification_number=? Hibernate: select d1_0.id,d1_0.additional_info,d1_0.identification_number,d1_0.image_path,d1_0.status,d1_0.type from documents d1_0 where d1_0.identification_number=? Message envoyé avec succès : com.google.firebase.messaging.BatchResponseImpl@4e45a8a Hibernate: insert into report_events (document_identifier,document_status,document_type,is_approved,latitude,longitude,scanned_at,scanned_by) values (?,?,?,?,?,?,?,?) 2025-12-11T15:10:43.314Z INFO 312252 --- [nio-9090-exec-1] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x000xee0x010x000x000xea0x030x030xc80x9e0xa90xa7=[0xd40xe3/z0xb80xc80x19#0xad40x8c0x950x88=0xa70xefc0x0e80xa30x990xf80x120xd90x960x96 ]. HTTP method names must be tokens at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:407) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:262) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:904) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-embed-core-10.1.26.jar!/:na] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) ~[tomcat-embed-core-10.1.26.jar!/:na] at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na] 2025-12-12T15:58:52.765Z INFO 312252 --- [io-9090-exec-10] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x000xee0x010x000x000xea0x030x03430x0d5E0xcfv0xa6g0x0a0x1eF+0xf50xa30xad0xa60xa90x8bf0xae0xe80x8d|