Identifying the cause of the problem accurately is
more important than solving the problem!

Application performance related issues may be caused by application’s environment configuration, flaws in logic, external configuration components connected to the application, and other factors. MaxGauge offers various functions for monitoring and analyzing such issues. In troubleshooting, we have divided the kinds of performance related problems that could commonly occur while operating an application into a few types, and put together a step by step guide for the process of troubleshooting the issues according to its type through MaxGauge. Please reference the Analysis Method by Type of Performance Issues below to help in your actual performance analysis through MaxGauge.

 

case_1_thumb

Case1. Analysis of Service Pauses Due to Full GC

When a Full GC occurs, the application run will temporarily pause and if it is prolonged, then it can cause a delay in the entire services, Because GC has a direct impact on the service, the GC Status Data is one of the important indicators in monitoring applications.

case_2_thumb

Case2. Analysis of Out of Memory Error Due to Excessive Fetching Jobs

Out of Memory occurs when the Carbage Collector is not able to make any space for creating new objects, and the Heap memory space cannot be expanded as well. This is a very critical issue because if the memory space becomes insufficient, then the application will not start its operation. For example. once a call is made, if there is a screen taking up more memory than the limit set for Heap Memory, it will result in an Out Of Memory Error in the Heap space.

case_3_thumb

Case3. Connection Pool Issues Due to Unreturned Connection Objects

After the use of JDBC connection, if the connection is not returned, then the corresponding connection does not get returned to the pool and becomes inaccessible for other service requests. Furthermore, the number of available connections in the pool will gradually decrease and will be exhausted at a particular point which may lead to delays in running the applications.

case_4_thumb

Case4. DB Lock Issues Due to Not Commit

After a DML execution in the DB, if a Commit or a Rollback execution is not done properly, it may lead to a delay in transaction processing time in the DB or a problem in the data consistency.