Troubleshooting server issues

You can use the Web interface to troubleshoot server issues.
You must be a member of the JazzAdmins group.
To troubleshoot server issues, click the Server tab. On this page, you can find server state information that can help you troubleshoot problems. The following table lists common problems and ways to troubleshoot them.

Problem

What to check

Database is not available

Click Admin, and then click Jazz Server Administration.

  • On the Server Status Summary page, in the Server Status pane, check that the database status is connected. If the status is unavailable, check the Database Status pane for details. Possible problems include an invalid database configuration and a valid configuration to a database that is not initialized.
    Note: The Derby database supports only one connection, so if another server instance is running, it might be using the only database connection. If this issue occurs, the Service Error Summary pane lists multiple errors.
  • In the Server VM pane, check that the server is running the correct JDK.
  • In the Service Error Summary pane, check for error messages.

Unable to change configuration properties

Check the server configuration properties: Expand Configuration and click one of these items:

  • E-mail Settings
  • Database Connections
  • Feed Settings
  • Advanced

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 only change configuration properties by editing the teamserver.properties file.

Failing services

Check the status of services: Click Component Status.

On the Installed Components 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.

Additional resources and tips

For more information, you can access the log feed:

If the log feed is not available, view the Apache Tomcat log file/tomcat/logs/catalina.out (Linux®) or the console window (win32).

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.

Ensure that the default Apache Tomcat connection ports 9080 and 9443 are not in use. The /conf/server.xml file defines the connection ports.

If the problems persist, consider reinstalling the database or the Web archive (WAR) file:


Feedback