Documentation on using EventDiagServlet page

[[email protected]]

Hi Everybody,

Does anybody have any documentation or more information on how to use the glog.webserver.event.EventDiagServlet page.

Links like Show events, Show threads, Mediators.

Please do let me know if you have more information this page.

Thanks and Regards,
Suresh

[chrisplough]

Re: Documentation on using EventDiagServlet page

You can find some more information on this Servlet within the following post:

http://www.otmfaq.com/forums/f27/performance-issue-integration-705/

In addition, here's a 10 second description:
http://<otm_server>/GC3/glog.webserver.event.EventDiagServlet

• Shows the thread queues in OTM - very important for performance tuning
• The most important columns are the Backlog (current processing backlog), Queue Size and Throughput
• All details are since the last restart and do not provide historical data
• Notation for most of the columns is: <average> / <high_water_mark>
• Backlogs aren't always bad (sometimes you need/want single-threaded queues) and adding threads isn't always a good thing (switching contexts, memory usage, etc).
• Click on the "Show Threads" button to view the individual threads for each queue.
• Use "Kill" with extreme prejudice, as you can't see exactly what process is
• running on that thread and the screen doesn't refresh in real-time.

Unfortunately, I'm not aware of any publicly available documentation to help. If you want to play with it and ask specific quesitons, I'm more than happy to answer.

Thanks,
--Chris

[[email protected]]

Re: Documentation on using EventDiagServlet page

Dear Chris,

Thankyou very much for the details provided. The information was very useful and would help me

Regards,
Suresh

[nick.polites]

Re: Documentation on using EventDiagServlet page

Also a few more things to note.

1) If you add a thread on this screen, you must close out of your browser before viewing the servlet again. If you simply refresh the screen, it will keep adding an additional threads.

2) Killing a thread will kill the process of that thread but will leave the thread in a hung state, meaning that no other activity can be processed by that thread until the next restart. You will need to add a thread to get around the kill.

3) As this and many other servlets are not officially supported by Oracle, you won't find any documentation out there on them from Oracle.