CODEWITHSUNDEEP
javahttpwebspheremonitoringpool
ctomek
ctomek

Reputation: 1786

How to monitor HTTP connections pool?

I have an application in WebSphere Application Server and I want to monitor HTTP connections pool (currently processed HTTP connections) and log this data to file. WebSphere Application Server has it's own monitoring tool, but as I see correctly there is no such parameter to monitor. It offers number of currently processed IIOP requests, servlet sessions, HTTP sessions, alive beans, concurrent outbound connection and some other statistics. Full info is is here

How can I monitor HTTP connections pool (currently processed HTTP connections) and log this data to file?

Upvotes: 4

Views: 6971

Answers (1)

Gas
Gas

Reputation: 18020

You are not entirely correct.

First you can monitor any thread pool that is in WAS via PMI. See here for counters that you may get from monitoring pool - http://www-01.ibm.com/support/knowledgecenter/api/content/nl/pl/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rprf_datacounter9.html

The thread pool is called WebContainer thread pool.

Second, you can store all these counters data to file directly using web admin console. Go to Monitoring and Tuning > Performance Viewer > Current activity, select server, then in PMI viewer select Settings > Log to define logging period and format. And in Modules > Thread pools > WebContainer you can view current counter values.

This is rather for short term monitoring, than for constant logging. There is also option to load and replay the log via console later, viewing gathered data.

These counters are of course available via JMX, so you can write your custom client if you need it.

UPDATE

If you are particularly interested in Web Serivces counters then there is separate Web Services monitoring module for that. Check this page for details Monitoring the performance of web services applications.

You will be able to see:

  • The number of requests dispatched to an implementation bean
  • The number of requests dispatched with successful replies
  • The average time in milliseconds to process full requests
  • The average time in milliseconds between receiving the request and dispatching it to the bean
  • The average time in milliseconds between the dispatch and receipt of a reply from the bean. This represents the time spent in business logic.
  • The average time in milliseconds between the receipt of a reply from a bean to the return of a result to the client
  • The average size of the SOAP request
  • The average size of the SOAP reply

Upvotes: 1

Related Questions