Spring Troubleshooting-Lower log levels

descriptive narrative of the problem1. After a change in the page, after the submission of the page 400 error, but the background is not output no matter what error message. 2. The debug listener should also have no response to the submission link on the page (no controller method in the background).

3. The browser refreshes the submit link to enter the background method (debug can be heard)
workaround: 1. By 3rd of the question, it is clear that the contents of the page must be a question of the number of references that cannot be submitted.

2. However, it is difficult to troubleshoot pages. I haven't seen anything unusual for 20 minutes. 3. Read some articles to receive the revelation. Want to try it by reducing the level of log. View more specific logs.

<root>          <level value= "Debug"/>          <appender-ref ref= "CONSOLE"/>          <appender-ref ref= " LogFile "/>      </root>

4. The problem was found because spring had a type mismatch error in processing the object's parameters.

The Shriekingtime is a date type in the train, but the page is a non-canonical form of the date "00:00"

@RequestMapping ("/addferrytrain") public String Addferrytrain (Train Train, httpservletrequest request)

Summary:This question itself is not too big problem, just by lowering the spring log level to troubleshoot the problem of the idea is very good, in the future projects can also be used for reference.

Spring Troubleshooting-Lower log levels