Investigate even further (thanks to Philippe Muletas this part was mostly borrowed from him) by :

logging to your CLM application Admin Web UI and check the Statistics.
It’s available at URL : http(s):<server:port>/<app>/admin#action=com.ibm.team.repository.admin.statistics
Example of URL : https://jts.mycompany.net:9443/jts/admin#action=com.ibm.team.repository.admin.statistics
Find out if any request has been running for an unexpectedly long time.
Note: you could get even more detailed information with URL: http(s):<server:port>/<app>/service/com.ibm.team.repository.service.internal.counters.ICounterContentService (already mentioned in version 2.x-related article : Tuning the Rational Team Concert 2.0 server ).

checking server heap utilization. Note that the server caches heavily and will utilize as much heap as possible, by design. So there could be an issue only if it’s near zero on multiple and consecutive refreshes.

If your CLM solution is deployed on IBM Websphere Application Server, you could also monitor your CLM applications with IBM Tivoli ITCAM which lets you :

Blog Feeds

Disclaimer

The postings on this site are my own. Anyone is free to use, copy, distribute, modify or sell the source code and other materials directly linked from sleroyblog.wordpress.com. It is provided "as is" without warranties. I am not responsible for any harm or damage caused to your computer, software or anything else caused by the material.