In fact, before this learning method has been thinking about, but persist for some time and did not stick to it. We all know that a good memory as bad written, bug this thing everywhere and at all times there, so before in peacetime have been thinking about is learning, the problems encountered and how to address are recorded, so next time if in case to the same problem, if you can remember how to solve it would be best, if you forget, you can also look at their own mistakes record, this is the real solution to a bug, do not let you troubled by the same bug. How to make yourself stick to it, I think the best is to write a blog, did not encounter a problem record, to reach a certain number on the release. Then began. I also just started, we encourage each other with it! Let the same bug does not appear.
一：在eclipse中启动tomcat时显示端口被占用
原因：有时候因为eclipse异常退出，但是tomcat还开着，这个时候，重新启动 eclipse，再次请求打开tomcat可能就会出现这种错误，端口被占用
解决方法：
1、在dos下查看是哪个程序占用了tomcat的端口
netstat -ano|findstr “8080”
可以查看到占用了8080端口号的进程号,比如为 1112
然后输入命令： tasklist|findstr “1112”
得到进程映射javaw.exe
启动任务管理器，在详细信息里面找到进程号为1112的javaw.exe，然后结束任务，问题就会解决
2、打开任务管理器，在进程中可以找到java.exe，直接关闭一般也是可以的
3、万能的重启（不到最后坚决不用hhh）
二：在eclipse中右击jar包没有显示built path选型，
这是由于视图引起的，解决方式就 是把packet explorer调出来。
三、在IDEA中贴上标签@Setter@Getter没有用
注意在IDEA中默认情况下是不支持注解的，所以我们要自己手动设置支持注解形式。 File -->Settings -->Build, Execution, Deployment -->Compiler -->Annotation Processors 后侧会出现有个Enable Annotation Processors 我们勾选上，然后完成，这样我们的工程就支持注解了。
Four: returned when using mybatis query is null
1, first check the database there is no data you want to check, if there is no certainty it will be empty
2, field names check the database and java entity class attribute name is not the same , if not the same and is not associated with the returned data certainly is null
five: when xshell recently installed software is always being given a lack of a .dll file
1, the file is installed in the C drive
2, install the missing .dll files specified installation path
today, in fact, no matter what the bug summary of it! The first step in panic, take a look at the following information, usually a clear error messages, and source code analysis. bug every day, learn to fix it every day, sooner or later immunization.
