Summary of recent bugs

There are not many codes in these two weeks , Because new demands have been overturned .

Record the production bug
1. The famous nullPointException.
performance ： The abnormal
How to locate ： For example, the exception prompt occurs in 30 That's ok , But the actual exception is in the 29 Line generated . So the newspaper 30 That's ok , It represents the end of the program 29 That's ok + Will execute the 30 I encountered a problem when I was ok .
reason ： Demand side （ This is an external demand ） Added a city , No sync to us . Leading to the front-end transmission to the city id It's time , We didn't find this in the Library id Corresponding information .
How to solve ： Synchronize to the demand side , Equal feedback .

2. Server startup module , Start exception
performance ： After script automation deployment , Prompt that the process is running , but ps -ef|grep Keyword without this process .
location ： Rerun the script , meanwhile tail -f Start log printing . If startup fails , There will be hints. .
reason ： Many people develop a branch , The deployment environment is test. The configuration file written by a member should be reasonable dev, Yes test, Yes prod, But he only wrote dev. Lead to @Value stay test In the deployment environment , Can't load test The value of the configuration file .
How to solve ： Two ways . Or deploy the environment test, increase test The configuration file . Or deploy dev Environmental Science , No need to add configuration files .