To troubleshoot server issues, in the Admin web client, click the Server tab. On this page, you can find server state information that can help you troubleshoot problems.
The table below lists common problems and ways to troubleshoot them.
Problem |
What to check |
---|---|
Database is not available |
Check the server status: click Status summary.
|
Unable to change configuration properties |
Check the server configuration properties: under Configuration, click one of the following items:
On these pages, you can view and update configuration properties. When you save changes to configuration properties, they are propagated to the teamserver.properties file. If the database is not connected, you can change configuration properties only by editing the teamserver.properties file. |
Failing services |
Check the status of services: click Component Status. On the Component Status page, check the stack trace for more information about failing services. |
Slow server activity |
Check the running services: click Active Services. On the Active Services page, check the running services and their stack traces. Check for services that run for an extended period of time. Check the server activity: click Statistics. On the Server Statistics page, check the server activity, such as statistics for web services, asynchronous tasks, and cache behavior. |
Modifying the profile.ini and license_profile.ini files
When running repotools commands or the start and stop server scripts from a directory other than the default, you should modify the URL property values to contain absolute directory paths.
url=file:jts/sites/update-site
Tourl=file:/opt/IBM/JazzTeamServer/server/conf/jts/sites/update-site
Additional resources and tips
For more information, you can access the log feed:
If the log feed is not available, view the Tomcat log file from a Windows console window or at JazzInstallDir/logs/jts.out, where JazzInstallDir is the location where you installed the server.
If the teamserver.properties file is not located during startup, the server does not work properly and the Tomcat log and log feed contains errors. The server.startup script provides the path to the property file.
If you are using Tomcat, ensure that the default Tomcat connection ports 9080 and 9443 are not in use by another application. The connection ports are defined in the installdir/tomcat/conf/server.xml file, where JazzInstallDir is the location where you installed the server.
If you are using WebSphere® Application Server, ensure that the WC_defaulthost (HTTP) and WC_defaulthost_secure (HTTPS) ports are not in use by another application. If you are an application server administrator, you can see the connection ports in the Integrated Solutions Console; click
.If the problems persist, consider reinstalling the database or the web archive (WAR) file. You can reinstall the database from the original distribution file (repositoryDB.zip) or from a backup file.
Watch videos CLM playlistJazz.net channel User Education channel |
Learn more CLM learning circleAgile learning circle Learning circles |
Ask questions Jazz.net forumdeveloperWorks forums |
Get support Support PortalDeployment wiki Support blog |