Home > Back-end >  Tomcat startup failure
Tomcat startup failure

Time:11-29

Error information below

24 - Feb - 2020 09:48:07. 856 information [HTTP - nio - 8080 - exec - 3] org. Apache. Coyote. Http11. Http11Processor. Service error parsing the HTTP request header
Note: further occurrences of the HTTP request parsing errors will be logged at the DEBUG level.
Java. Lang. IllegalArgumentException: string found in the method name is invalid, the HTTP method name must be valid symbols.
The at org. Apache. Coyote. Http11. Http11InputBuffer. ParseRequestLine (Http11InputBuffer. Java: 415)
At org. Apache. Coyote. Http11. Http11Processor. Service (260) Http11Processor. Java:
The at org. Apache. Coyote. AbstractProcessorLight. Process (AbstractProcessorLight. Java: 65)
The at org. Apache. Coyote. AbstractProtocol $ConnectionHandler. Process (AbstractProtocol. Java: 860)
At org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun NioEndpoint. Java: (1591)
The at org.apache.tomcat.util.net.SocketProcessorBase.run (SocketProcessorBase. Java: 49)
The at Java. Util. Concurrent. ThreadPoolExecutor. RunWorker (ThreadPoolExecutor. Java: 1142)
The at Java. Util. Concurrent. ThreadPoolExecutor $Worker. The run (ThreadPoolExecutor. Java: 617)
At org, apache tomcat. Util. Threads. TaskThread $WrappingRunnable. Run (61) TaskThread. Java:
The at Java. Lang. Thread. The run (Thread. Java: 748)
24 - Feb - 2020 09:48:07. 860 information [HTTP - nio - 8080 - exec - 4] org. Apache. Coyote. Http11. Http11Processor. Service error parsing the HTTP request header
Note: further occurrences of the HTTP request parsing errors will be logged at the DEBUG level.
Java. Lang. IllegalArgumentException: string found in the method name is invalid, the HTTP method name must be valid symbols.
The at org. Apache. Coyote. Http11. Http11InputBuffer. ParseRequestLine (Http11InputBuffer. Java: 415)
At org. Apache. Coyote. Http11. Http11Processor. Service (260) Http11Processor. Java:
The at org. Apache. Coyote. AbstractProcessorLight. Process (AbstractProcessorLight. Java: 65)
The at org. Apache. Coyote. AbstractProtocol $ConnectionHandler. Process (AbstractProtocol. Java: 860)
At org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun NioEndpoint. Java: (1591)
The at org.apache.tomcat.util.net.SocketProcessorBase.run (SocketProcessorBase. Java: 49)
The at Java. Util. Concurrent. ThreadPoolExecutor. RunWorker (ThreadPoolExecutor. Java: 1142)
The at Java. Util. Concurrent. ThreadPoolExecutor $Worker. The run (ThreadPoolExecutor. Java: 617)
At org, apache tomcat. Util. Threads. TaskThread $WrappingRunnable. Run (61) TaskThread. Java:
The at Java. Lang. Thread. The run (Thread. Java: 748)

CodePudding user response:

May I have your problem solved? Particularly nasty see please reply. Thanks

CodePudding user response:

Your error description is too abstract, not stick your HTTP request information? I mean there are a lot of things will lead to the abnormal, suggest you attach more information, example: the requested url, and the parameters of the request, the type of request, the server's response information

CodePudding user response:

Look at this address:
 
http://127.0.0.1:10080/dlq/updprat? Jsonparams={% 22 datavz % 22: % 18% 2209/04/20 2014: thou % 22, % 22 descavz % 22: % 22 foo % 20 foo % 22, % 22 idprat % 22:32, % 22 codprat % 22:22123456% % 22,... etc... Costs, % 22: []} & amp; PratAffidateSearchType=a

There are illegal characters, can result in tomcat: The valid characters are defined in RFC 7230 and RFC 3986

CodePudding user response:

Open the Java file using notepad, save it, choose utf-8 encoding, the penultimate,
Use the IDE to open this file to try again,
  • Related