Troubleshooting server issues

You can use the administrative Web interface to troubleshoot server issues.

Before you begin

You must be logged in to the Admin Web UI and be a member of the JazzAdmins group.

About this task

To troubleshoot server issues, in the Admin Web UI, click the Server tab. On this page, you can find server state information that can help you troubleshoot problems.

Tip: Go to Jazz.net Tech Notes or Server troubleshooting FAQ to find additional troubleshooting tips.

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.

  • On the Status Summary page, in the Server Status pane, verify that the database status is connected. If the status is unavailable, check the Database Status pane for details. Possible failures include a database configuration that is not valid and a valid configuration to a database that is not initialized.
    Note: The Derby database supports only one connection; if another server instance is running, it might be using the only database connection. If this problem occurs, the Service Error Summary pane lists multiple errors.
  • In the Server VM pane, verify 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: under Configuration, click one of the following items:

  • E-mail Settings
  • Database Connections
  • Feed Settings
  • License Key Management
  • Advanced Properties

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.

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/jazz.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.

Ensure that the default Tomcat connection ports 9080 and 9443 are not in use. The connection ports are defined in the installdir/tomcat/conf/server.xml file, where JazzInstallDir is the location where you installed the server.

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.


Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug