A great wisdom in life is a good grasp of mistakes. On the one hand we should not be afraid to make mistakes when doing things, look for things to think, to be courageous not to act timid, afraid to make mistakes will make people lose a lot of good opportunities. The other is to try to avoid mistakes, do more wrong, especially in terms of investment, as Buffett said, the most important thing is to avoid investment mistakes, keep the principal. Points there is a good balance of risks and benefits, should be good reflective learning from mistakes, either their own or someone else's fault turn, can be converted into their lessons.
Life should spend time and energy on things they do best. Tian Ji's horse racing story with inferior horses and fine horses than others, the result is far inferior, so how you could get good at something unfamiliar and familiar to people than good at these things do?
By default, Spring Boot the log output to the console, not to the log file. If you want to write the log file other than the console output, you need to set logging.file or logging.path property in application.yml in. But maybe when the properties configure only logging.file take effect!
Production environment will be equipped with a separate log file, if you want to read in application.xml property in the log file to note: logback.xml early loaded application.yml, logback-spring.xml night if logback configuration required to load application.yml use application.yml attributes, you need to be named logback-spring.xml. And using springProperty logback application.yml in order to use value, such as: <springProperty scope = "context" name = "logPath" source = "log.path" defaultValue = "logs" />
Large community means more support, a wide ecosystem of frameworks, libraries, and other tools of composition.
Java is ubiquitous, it is widely used in various applications. As long as the development of Java applications is still in use, then we can say, Java is still viable. This also means that the needs of Java developers will continue for a long time.
use under linux top -Hp pid (shift + p to sort by cpu, shift + m by memory sorting) command, you can
get into this process all of the following thread resource consumption, by looking at the% CPU it is to find the most CPU-intensive thread PID, and under Windows Explorer can not see to thread the case, you need to
find the resources occupancy thread this process with processExplorer tool.
When the server 302 in response to the browser, the browser is not directly ajax callback handler, but first performs a 302 redirect - Location information is read from the Response Headers, and then sends a request to the Location Url, closing after the response to this request will be ajax callbacks.