Use of JSP pages the debug directory --Sun IDM
http://<idm-instance>:port/debug/<Jsp> . Where <idm-instance> is your instance and <port> is your port.
callTimers.jsp. What this does is provide a interface for basic method profiling. In here you can take a look at what is being called how many time and how long . You can even click on the method to see what is calling it.
The best way to collect this is to:
\* go to debug/callTimer.jsp
\* clear the timer
\* start the timer
\* after 15 minutes stop the timer
\* Export the results and send back the .xml file.
Below is a sample of what the CallTimer.jsp page looks like
This second picture is when you click on a method
Now, lets talk about a few others
codeId.jsp
What this does is displays the codeId value for a specified class. This also lists the location of the class . For this one you need to know what class to add in the class box. For this example I chose the IDMResourceAdapter in her you can see the codeId and where the class was called from.
Gateway.jsp is a page that lists all the debugging info . In here you can choose which gateway to display . You can also get the version of the gateway and also turn on tracing on the gateway. Only certain resource adapters use the gateway (AD,Novell) .
Show_Memory.jsp - This shows the used and total memory used on the system. To make this accurate you need to hit the garbage collection button. This is good for memory issues.
Show_WSProp.jsp is a page that displays the attributes in the Waveset.properties file. Quick and easy way to make changes . One thing to note is that changes in this page only last until the next server restart. If you need to make permenant changes edit the file.
SysInfo.jsp - This is a pretty cool tool. What it does is display all the java properties for the instance.
Show_Reconciler.jsp is a good one to see what is going on with your recons. In this page you can see the pending recons and also the minimum and maximum recon thread and worker threads you have running. In my case I am not running any recons or have any scheduled so I am not seeing any.
The last one and probably the most requested by support is the Show_Timings.jsp.
What this one shows is the current time the system is spending processing the classes. The best way to get accurate info is to do
\* go to debug/ShowTimings.jsp
\* clear the timer
\* start the timer
\* start the event that was taking a long time
\* after 15 minutes stop the timer
\* Cut and paste the results to an excel spreadsheet and send.
In the jsp page or the spreadsheet, You will see the class , If you have methodtimer set to true you will see a detail link that shows the class name and the stack traces.
The History link shows a graph of the recent data points and the history data shows the data collected by the system.
In the spreadsheet, you will see the amount of calls , any errors,and the Average time, Min and Max times as well. What you should look for is ones that are being called a ton of times and then ones that the average time is huge.
(Note: most time attrs are in msec 10mins = 60000msec)
. Please leave me comments for you feedback
callTimers.jsp. What this does is provide a interface for basic method profiling. In here you can take a look at what is being called how many time and how long . You can even click on the method to see what is calling it.
The best way to collect this is to:
\* go to debug/callTimer.jsp
\* clear the timer
\* start the timer
\* after 15 minutes stop the timer
\* Export the results and send back the .xml file.
Below is a sample of what the CallTimer.jsp page looks like
This second picture is when you click on a method
Now, lets talk about a few others
codeId.jsp
What this does is displays the codeId value for a specified class. This also lists the location of the class . For this one you need to know what class to add in the class box. For this example I chose the IDMResourceAdapter in her you can see the codeId and where the class was called from.
Gateway.jsp is a page that lists all the debugging info . In here you can choose which gateway to display . You can also get the version of the gateway and also turn on tracing on the gateway. Only certain resource adapters use the gateway (AD,Novell) .
Show_Memory.jsp - This shows the used and total memory used on the system. To make this accurate you need to hit the garbage collection button. This is good for memory issues.
Show_WSProp.jsp is a page that displays the attributes in the Waveset.properties file. Quick and easy way to make changes . One thing to note is that changes in this page only last until the next server restart. If you need to make permenant changes edit the file.
SysInfo.jsp - This is a pretty cool tool. What it does is display all the java properties for the instance.
Show_Reconciler.jsp is a good one to see what is going on with your recons. In this page you can see the pending recons and also the minimum and maximum recon thread and worker threads you have running. In my case I am not running any recons or have any scheduled so I am not seeing any.
The last one and probably the most requested by support is the Show_Timings.jsp.
What this one shows is the current time the system is spending processing the classes. The best way to get accurate info is to do
\* go to debug/ShowTimings.jsp
\* clear the timer
\* start the timer
\* start the event that was taking a long time
\* after 15 minutes stop the timer
\* Cut and paste the results to an excel spreadsheet and send.
In the jsp page or the spreadsheet, You will see the class , If you have methodtimer set to true you will see a detail link that shows the class name and the stack traces.
The History link shows a graph of the recent data points and the history data shows the data collected by the system.
In the spreadsheet, you will see the amount of calls , any errors,and the Average time, Min and Max times as well. What you should look for is ones that are being called a ton of times and then ones that the average time is huge.
(Note: most time attrs are in msec 10mins = 60000msec)
. Please leave me comments for you feedback
No comments:
Post a Comment