At the beginning of this, there was a problem that the response performance of a certain screen of a web application was slow. I started the investigation from the help that there was no response from the application when I played with various things from the junior who was entrusted with building the environment. The cause has been resolved, but I received a request to know the logic for identifying the cause. Since this area was solved by sensory knowledge, I will output it with the meaning of summarizing it.
Java stopped working by increasing the maximum heap size of java, which is an AP server. The memory used by the OS was free, but Java did not start. When the JDK is 32bit, I knew that the upper limit of the maximum number of memory used was small, so I came up with a solution.
I identified it from the error log, but forgot to copy the error log.
Doubt the counselor Ask the counselor "What happened and what happened?" To check the reproducibility. If it can be returned, return it to the state before the work and have the work reproduced If you can't get it back, reverse the procedure to see where the event occurred (debug?)
See what's happening inside the application Check the log to see what's happening Check the following for log check of both AP server and application
I thought that there was no factor that lowered productivity as much as the personalization of knowledge and technology. I was committing that stupidity. I will continue to post dirty articles in the future.