How to take a connection dump for analyzing performance issues?
For Performance/slowness issues instead of taking Threaddump manually or instead of invoking PerformanceTool make use of the below URL when the issue occurs,
Note: The above URL works even when the server is not responding.
Invoking the above URL collects the below outputs,
ThreadDump
RunningQueries
LockedQueries
ConnectionDump
at the time of the issue occurrence and automatically place it in the logs folder in the SupportCenter directory
Once the above files are generated the below message will be shown in the browser,
--- Successfully generated debug log files. Please zip the entire 'logs' folder present in ManageEngine/SupportCenter/ and upload it using the below link.
New to ADSelfService Plus?
Related Articles
Inputs required for analyzing Performance Issues
We need a couple of details to analyze Performance issue. So, please send the below details : Below mentioned details should be gathered before restarting the application. 1. Let us know whether you are taking Scheduled full backup or backup without ...Steps to take PGSQL Dump Backup and Restore
PGSQL – DUMP – Backup Procedure : Login to the MSP application server and perform the below steps, 1. Start the application To take Postgres (Psql) Dump : 3. Open a command prompt and navigate into <ServiceDeskPlus-MSP>/pgsql/bin directory. 4. ...How to enable Performance monitoring tool ?
To analyze Performance issues, logs and tuning alone won't be sufficient. Hence, we need to follow a few steps to enable the Performance Monitoring tool, which will monitor the application's performance and automatically collects the data when the ...Performance Debug
For Performance/slowness issues instead of taking Threaddump manually or instead of invoking PerformanceTool make use of the below URL when the issue occurs, http://servername:portnumber/servlet/PerformanceDebug The above URL works even when the ...Performance debugging from version 9306 onwards
On Performance/Crash Issues, we have one URL to generate all debug details, this is applicable from 9306 onwards. Need to execute the URL in the browser, which has already login session into the application ...