1. Check if the project is started in debug mode, which is the button with the bug in the picture.
2. Check to see if breakpoints are disabled, disable the breakpoint and show the Gray
3. Add an output statement at the end of the breakpoint to determine whether you are entering a breakpoint (you need to have access requests for Web projects to reach some breakpoints)
4. Breakpoint hit wrong, idea seems to automatically identify invalid lines, such as String a=null; this kind of break point does not make sense of things.
5.Rebuild the entire project, then debug mode boot
6. For some first time valid, the second invalid situation, may refer to this way, http://bbs.csdn.net/topics/392003661
7. You can also write a test case to check if your idea's debug is working properly.
8. In the end, for some Web projects, you can try a different version of Tomcat. Or simply change the idea, suggest using the flagship (ultimate) ideas, and don't use the Community version (Community) (my test case can debug normally, and set breakpoints at the controller of the Web layer. Debugging directly into the breakpoint at the method, print out the log and get data back to the front, but it is at the breakpoint stop, and finally there is no way to change a flagship version of idea.