tc Server

Available only in vFabric Hyperic

Configure a tc Server Instance

The features described on this page are available in tc Server and tc Server Standard Edition.

tc Runtime Configuration

On this page you can configure the selected tc Runtime instance.

Saving or Undoing Changes

HQ populates the fields of the tc Runtime configuration pages from the its configuration files, including:

  • conf/server.xml

  • conf/context.xml

  • conf/web.xml

  • bin/setenv.sh

  • conf/catalina.properties

  • conf/logging.properties

(All relative to CATALINA_BASE, the root directory of the tc Runtime instance.)

Each configuration page includes a Save button for saving the changes made in the user interface to the tc Runtime configuration files. If you try to navigate to a different page without saving any of your updates, HQ asks you if you want to leave the page and lose these updates.

When you click Save to save your changes, a box labeled "Changes have been made locally" is displayed until you click either:

  • Push - to write the configuration changes you have made to the appropriate tc Runtime configuration file (such as server.xml). If you push the changes, HQ overwrites existing configuration, saving a backup of the overwritten configuration. Most saved changes to the tc Runtime configuration require a server restart to take effect; HQ flags these cases and provides a link to easily restart the tc Runtime.

  • Undo - to undo all changes that have been made since the last push or undo.

If you update tc Runtime configuration settings from the HQ user interface, do NOT manually update the tc Runtime configuration files at the same time. HQ clears its local memory and reloads the configuration files upon certain events, not continuously.

User Permissions Required to Use the tc Runtime Features

The HQ super-user can use all the tc Runtime features of the HQ UI.  If, however, you log on to the HQ UI as a non-super-user, then that user must have certain permissions to be able to use the tc Runtime features, as described in this section.

In HQ, users are assigned roles, which in turn are assigned permissions, such as View and Control. For information about users and roles, see User Accounts and Roles in Hyperic.

The following table describes the additional effects that some of the HQ permissions have on the tc Runtime features. Use this table to determine which role you should assign a user that will be managing tc Runtime instances.

Permission

Additional Effect on tc Server HQ Plugin Features

View

Allows the user to:

  • View the deployed Web applications in the Views > Application Management tab.

  • View the current configuration of a tc Runtime instance in the Views > Server Configuration tab.

Modify

Allows the user to:

  • Update the fields in the Views > Server Configuration tab and then push the data to the configuration files associated with the tc Runtime instance, such as server.xml.

  • Use the application lifecycle commands of the Views > Application Management tab to start, stop, reload, or undeploy a Web application.

Control

Allows the user to use the commands in the Control tab to start, stop, and restart a tc Runtime instance.

Configuring General tc Runtime Options

The main tc Runtime configuration page includes options to change the Shutdown Port and Shutdown Command.

  1. Navigate to the configuration pages for the tc Runtime instance. For instructions, see Navigating tc Runtime Configuration Pages.

  2. Click the Configuration tab.

  3. Click the General link in the list on the left. For information about the fields on the page, see tc Runtime Configuration Reference.

  4. Make your changes.

  5. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

  6. To write your changes to the tc Runtime configuration files, click Push in the "Changes have been made locally" box. See Saving or Undoing Changes.

For additional detailed information about configuring the tc Runtime, see The Server Component, in Apache Tomcat documentation.

Configuring Startup Options

The page for configuring tc Runtime Start settings includes options for configuring the JVM where the instance runs, including minimum and maximum heap size, garbage collection, and debugging options.

NOTE: HQ populates the tc Runtime Start page with information from the CATALINA_HOME/bin/setenv.sh file of the server instance you are configuring (specifically the JVM_OPTS environment variable.) If you have not set the JVM_OPTS environment variable in this file, then the fields in the Server Start page will be blank.

The page allows you to add your own command line arguments to the JVM; be careful using this option because HQ does not validate the options but simply adds them to the Java command that starts the tc Runtime instance. If you enter them incorrectly, you will get an error starting the tc Runtime instance.

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Configuration tab.

  3. Click the Server Start link in the list on the left. For information about the fields on this page, see ui-tcserver.ServerConfigurationRef.

  4. Make your changes. 

  5. To add your own JVM command line arguments, click the Advanced link at the bottom and enter them in the form the form "-Xoptionvalue or -XX:option=value, separating options with a space.

  6. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

  7. To write your changes to the tc Runtime configuration files, click Push in the "Changes have been made locally" box. See Saving or Undoing Changes.

Configuring the Context Container

Use this page to configure the context for every Web application deployed to this tc Runtime instance.

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Configuration tab.

  3. Click the Context Container link in the list on the left.

  4. Make your changes. For reference information about the fields on this page, see tc Runtime Configuration Reference.

  5. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

  6. To write your changes to the tc Runtime configuration files, click Push in the "Changes have been made locally" box. See Saving or Undoing Changes.

For additional detailed information about configuring the context container for tc Runtime, see The Context Container, part of the general Apache Tomcat documentation.

Configuring JSP Options

SpringSource tc Runtime implements version 2.1 of the Java Server Pages (JSP) specification. Use this page to configure the behavior of the JSPs that are deployed to a tc Runtime instance.

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Configuration tab.

  3. Click the Server Defaults: JSP link in the list on the left.

  4. Make your changes. For information about the fields on this page, see tc Runtime Configuration Reference.

  5. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

  6. To write your changes to the tc Runtime configuration files, click Push in the "Changes have been made locally" box. See Saving or Undoing Changes.

For more information about configuring the behavior of JSPs in tc Runtime, see Jasper 2 JSP Engine How To, part of Apache Tomcat documentation.

Configuring Static Content Defaults

Use this page to configure the behavior of static content in Web applications that run on tc Runtime.

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Configuration tab.

  3. Click the Server Defaults: Static Content link in the list on the left.

  4. Make your changes. For  information about the fields on this page, see tc Runtime Configuration Reference.

  5. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

  6. To write your changes to the tc Runtime configuration files, click Push in the "Changes have been made locally" box. See Saving or Undoing Changes.

For additional detailed information about configuring the behavior of static content in tc Runtime, see Default Servlet Reference, part of the general Apache Tomcat documentation.

Using the Advanced Server Configuration Options

The Advanced section of the main Server Configuration tab includes options for reverting or reloading configuration values in the event you do not want to save any of the recent updates you have made using the HQ user interface. The Advanced section also includes an option to upload a local configuration file in its entirety, such as server.xml. The following sections provide more information about these options.

SpringSource recommends that you use these options with caution.

Reloading Settings From Server

Click the Reload Settings From Server link if you want to reload the server configuration currently contained in the tc Runtime configuration files. With this option, all local changes to the tc Runtime instance you have made using the HQ user interface that you have not yet pushed to the instance will be lost.

Reverting to a Previously Saved Configuration

Click the Revert To a Previously Saved Configuration link if you want to revert to the most recent backup copy of the tc Runtime configuration. Each time you push changes from the HQ user interface to the tc Runtime configuration files, the tc Server HQ plugin makes a timestamped backup copy of the previous configuration before overwriting the relevant configuration file, such as server.xml. With this option, you can revert back to the most recent backup copy in the event that there was a problem with the most recent changes that you pushed. As with reloading the current configuration, if you revert to a backup copy, any local changes to the tc Runtime instance made using the HQ user interface will be lost.

If you have never pushed configuration changes from the HQ UI to the tc Runtime instance, then no backup file will exist to which the tc Server HQ plugin can revert. In this case, if you try to revert, you will get an error.

Uploading a Configuration File

Click the Upload a Configuration File link to upload a local configuration file, such as server.xml, and copy it to the appropriate tc Runtime instance directory. Use the Configuration File drop-down list to specify the type of configuration file you are going to upload, and then use the Browse button to browse for the file on your local computer.

The tc Server HQ plugin makes a timestamped backup copy of the current configuration file before it overwrites it with the one you uploaded. This means that you can revert to the backup copy in the event that you do not want to use the uploaded configuration file for some reason.

Configuring and Creating JDBC Data Sources

JDBC datasources make it easy for a user to access data in a database server. A datasource defines a pool of JDBC connections which in turn connect to a specific database using a specified URL, username, and so on. Use this page to create and configure configure datasources.

You can create two types of JDBC data sources:

  • Database Connection Pool (DBCP) Datasource — The DBCP Datasource is the standard datasource provided by tc Runtime that uses the commons-dbcp package. Although this datasource is adequate for simple applications, it is single-threaded which means that in order to be thread-safe, tc Runtime must lock the entire pool, even during query validation. Thus it is not suitable for highly concurrent environments. Additionally, it can be slow, which in turn can negatively affect the performance of Web applications.

  • Tomcat Datasource — The Tomcat Datasource includes all the functionality of the DBCP datasource, but adds additional features to support highly-concurrent environments and multiple core/cpu systems. The Tomcat datasource typically performs much better than the DBCP datasource. Additional features include:

    • Dynamic implementation of the interfaces, which means that the datasource supports the java.sql and javax.sql interfaces for your runtime environment (as long as your JDBC driver supports it), even when compiled with a lower version of the JDK.

    • Validation intervals so that tc Runtime doesn't have to validate every single time the application uses the connection, which improves performance.

    • Run-Once query, which is a configurable query that the tc Runtime instance runs only once when the connection to the database is established. This is very useful to setup session settings that you want to exist during the entire time the connection is established.

    • Ability to configure custom interceptors to enhance the functionality of the datasource. You can use interceptors to gather query stats, cache session states, reconnect the connection upon failures, retry queries, cache query results, and so on. The interceptors are dynamic and not tied to a JDK version of a java.sql/javax.sql interface.

    • Asynchronous connection retrieval - you can queue your request for a connection and receive a Future back.

To create a new JDBC datasource, or edit an existing one:

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Resources tab.

  3. Click the JDBC Data Sources link in the list on the left.

  4. If you want to edit an existing data source, click its name in the table and make your changes. If you want to create a new one, click the Create a New Tomcat/DBCP Data Source link. For information about the fields on this page, see tc Runtime JDBC Reference.

  5. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

  6. To write your changes to the tc Runtime configuration files, click Push in the "Changes have been made locally" box. See Saving or Undoing Changes.

For more information about configuring JDBC data sources, see JNDI Datasource HOW-TO, part of Apache Tomcat documentation.

Configuring and Creating tc Runtime Services

A tc Runtime service represents the combination of one or more connector components that share a single engine component for processing incoming requests. A tc Runtime instance can have one or more services configured. The default service is "catalina".

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Services tab.

  3. If you want to edit an existing service, such as the default "catalina" service, click its name in the table and then configure, or add, the following components of the service:

  4. If you want to create a new service, click the New Service link. For information about the fields on the Create a New Service page, see tc Runtime Service Reference.

  5. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

For more information about configuring tc Runtime services, see The Service Component, part of Apache Tomcat documentation.

Configuring and Creating Connectors


Connectors represent the interface between external clients sending requests to (and receiving responses from) a particular tc Runtime service. A tc Runtime instance can have one or more connectors, one for each supported message protocol. The default connector, configured for each tc Runtime, is the HTTP connector.

Use this page to configure, or create new, connectors for the current tc Runtime service.

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Services tab.

  3. In the Services table, click the name of the service for which you want to configure or create a connector.

  4. Click the Connectors link in the list on the left.

  5. If you want to edit an existing connector, click its name in the table and make your changes. If you want to create a new one, click the New AJP Connector or New HTTP(S) Connector link, depending on the type of connector you want to create. For information about the fields on this page, see tc Runtime Services Reference.

  6. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

For additional detailed information about configuring tc Runtime connectors, see Connectors How-To, part of the general Apache Tomcat documentation.

Configuring and Creating Virtual Hosts

A tc Runtime host represents a virtual host, which is an association of a network name for a server (such as "www.mycompany.com") with the particular computer which hosts the tc Runtime instance. In order to be effective, this name must be registered in the Domain Name Service (DNS) server that manages your Internet domain.

Use this page to configure, or create new, virtual hosts for the current tc Runtime service.

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Services tab.

  3. In the Services table, click the name of the service for which you want to configure or create a virtual host.

  4. Click the Hosts link in the list on the left.

  5. If you want to edit an existing host, click its name in the table and make your changes. If you want to create a new one, click the New Host link. For reference information about the fields on this page, see tc Runtime Services Reference.

  6. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

For more information about configuring tc Runtime hosts, see The Host Container, part of Apache Tomcat documentation.

Configuring tc Runtime Logging

Use this page to configure the logging system for the current engine. Note that you can also configure logging for a host by configuring the specific Host component; see Configuring and Creating Virtual Hosts.

  1. Navigate to the tc Runtime configuration pages.

  2. Click the Services tab.

  3. In the Services table, click the name of the service for which you want to configure logging.

  4. Click the Logging link in the list on the left.

  5. Make your changes in the table. For information about the fields on this page, see ui-tcserver.ServerServicesRef.

  6. Click Save. The message "Configuration saved successfully" indicates your changes were successfully saved.

For more information about configuring tc Runtime logging, see Logging in Tomcat, part of the general Apache Tomcat documentation.

Manage tc Server Applications

This page describes page the tc Server Application Management view in the VMware vFabric™ Hyperic® user interface enabled by the tc Server user interface plugin. This page is present in the Hyperic user interface only if have the plugin.

tc Runtime Application Management

The Application Management page, available when a tc Runtime instance or a group of tc Runtime instances is selected, enables an authorized user to manage applications deployed that server instance or group.

The HQ super-user can use all the tc Runtime Application Management features of the HQ UI.  If, however, you log on to the HQ UI as a non-super-user, then that user must have certain permissions to be able to use the tc Runtime features.  See User Permissions Required to Use the tc Runtime Features for details.

An HQ Group is not a Cluster

An HQ group is not equivalent or similar to a tc Runtime cluster.

  • An HQ group is a set of other managed resources. An authorized user can create a group and assign resources to it. A group whose members are all of the same resource type is referred to as a compatible group. You can manage and monitor the resources in a compatible group at the group level. Grouping tc Runtime instances allows you manage applications across multiple tc Runtime instances.

  • A tc Runtime cluster enables session replication. Clustering behavior is defined in a tc Runtime instance's server.xml file.

Navigating to a tc Runtime Instance Or Group

To navigate to the Application Management page of a tc Runtime instance or group.

  1. Click Resources > Browse at the top of the HQ Dashboard.

    • To browse to a server instance:

      • Click Servers to view a list of of the servers to which you have access.  tc Runtime instances have the server type "SpringSource tc Runtime 6.0". Apache Tomcat server instances have the server type "Tomcat X.X".

    • To browse to a group of servers:

      • Click Compatible Groups/Clusters to view a list all the compatible groups to which you have access. Groups of tc Runtime have the type "SpringSource tc Runtime 6.0".

  2. In the table, click the name of the tc Runtime instance or group to which you want to navigate.

  3. Click Views > Application Management.

Creating tc Runtime Groups

Grouping tc Runtime instances eases the process of managing server instances and applications. For example, you can deploy an application to group of tc Runtime with a single command, instead of deploying to each instance individually. To create a group of tc Runtime instances:

  1. Click Resources > Browse at the top of the HQ Dashboard.

  2. Click Servers to list servers in inventory to which you have access. (Note: Only server instances that have been auto-discovered by HQ and added to inventory appear). tc Runtime instances have the server type "SpringSource tc Runtime 6.0". Apache Tomcat server instances have the server type "Tomcat X.X".

  3. Check the box to the left of each tc Runtime instance you want to include in the new group.

  4. Click Group.

  5. Enter a name for the group (required) and a description and location as desired.

  6. Click OK.

Listing Applications

Navigate to the Application Management page for a server instance or group. Deployed applications are listed in the Deployed Applications section of the page. For a group, the table lists all applications deployed to all servers in the group. The table shows:

  • Status - The state of the application - either "Running" or "Stopped".  For a group of servers:

    • "Running" or "Stopped" indicates that all instances of the application on all servers in the group have that state.

    • A numeric value indicates the number of servers upon which the application's state is "Running".

  • Sessions - The number of current active sessions for the application.

NOTE: Only applications on running tc Runtime instances appear.  HQ returns an error for application hosts that are not running.

Deploying Applications

Deploying an application is the process of uploading it to tc Runtime and making it available to users. You can deploy an application to a single tc Runtime instance or to a group of tc Runtime instances. If you deploy to a group, the application will be deployed to each of tc Runtime instance in that group, enabling users to run the application from any of the tc Runtime instances in the group.

You can deploy an application from a WAR file located:

  • on your local file system (on the the same machine as the browser you are using to connect to HQ's web user interface), or 

  • on the computer on which the tc Runtime resource is running.

Whether the WAR file is local or remote, you can either enter a new context path (string that uniquely identifies the Web application in the URL used to invoke it), or use the default value, which is the name of the WAR file, without the".war" extension.

  1. Navigate to the Application Management page for a tc Runtime instance or group.

  2. Depending on the location of the WAR file for the application, either:

    • Click Browse in the Deploy Application From Local Machine section to browse to the file's location.

    • Enter the full path to the WAR file on the computer hosting the tc Runtime resource in the Deploy Application from Server Machine section.

  3. As desired, enter a context path in the Context path text box.

  4. Optionally check the Use cold deployment strategy if you want the tc Runtime instance to shutdown, deploy the application, and then start up again. By default (if box is unchecked), the tc Runtime instance hot-deploys the application, which means it does not shutdown then restart but simply deploys the application while the instance is still running. Use the cold deployment strategy if you want to avoid common hot deployment errors, such as running out of PermGen space. The PermGen space holds the metadata about classes that have been loaded/created in the JVM.

  5. Click Upload and Deploy or Deploy, whichever is appropriate.

  6. See the top "Results of the last operation" section for details about the result of deploying the application. When you deploy an application to tc Runtime, the application is started.

Undeploying Applications

Undeploying an application removes it from the tc Runtime instance or group. If you want to temporarily prevent users from access an application, stop it rather than undeploy it. See Stopping Applications.

  1. Navigate to the application management page of a tc Runtime instance or group.

  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to undeploy.

  3. Click Undeploy. HQ removes the application from the list of deployed applications.

  4. See the top "Results of the last operation" section for details about the results of undeploying the application.

Starting Applications

Starting an application makes it available to users. You must have previously deployed the application to be able to start it.

  1. Navigate to the application management page of a tc Runtime instance or group.

  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to start.

  3. Click Start. The status of the application changes to "Running".

  4. See the top "Results of the last operation" section for details about the result of starting the application.

Stopping Applications

Stopping an application makes it unavailable to users.

  1. Navigate to the application management page of a tc Runtime instance or group.

  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to stop.

  3. Click Stop. The status of the application changes to "Stopped".

  4. See the top "Results of the last operation" section for details about the result of stopping the application.

Reloading Applications

When you reload an existing application, it shuts itself down and then reloads itself. For additional details, see Reload an Existing Application on the Apache Tomcat 6.0 Web site.

  1. Navigate to the application management page of a tc Runtime instance or group.

  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to reload.

  3. Click Reload. The status of the application changes to "Running."

  4. See the top "Results of the last operation" section for details about the result of reloading the application.

tc Runtime Configuration Reference

This page defines the fields on the Views > Server Configuration > Configuration tab - the page where an authorized user can configure a tc Runtime instance.

General Configuration

Server Properties

Field Name

Description

Shutdown Port

The TCP/IP port where the tc Runtime instance listens for a shutdown command. The connection must be initiated from the same server computer that is running this instance of tc Runtime.

Valid values are -1, 1, 2, ... up to  65535.

With the default setting, "-1", no shutdown port is enabled, so that the only way the server instance can be shut down is by a local "kill" statement to the server process.

Shutdown Command

The command to issue via a TCP/IP connection to the Shutdown Port to shut down tc Runtime.

JMX Listener

The JMX Listener section configures the component of the tc Runtime instance that listens for Java Management Extensions (JMX) connections from management tools, such as the Hyperic Agent. By default, tc Runtime enables JMX connectivity.

Field Name

Description

Enabled

Specifies whether the tc Runtime instance's pre-configured JMX listener is enabled.

Important: The Hyperic Agent uses JMX to connect to tc Runtime, so if you disable the JMX listener then you will not be able to use configure tc Runtime instances or groups from the Hyperic user interface, unless you configure JMX for tc Runtime through some other mechanism.

Port

Specifies the port upon which tc Runtime listens for JMX/RMI connections. Specify a port number that is not in use by another process.

IP Address

Specifies the IP address upon which tc Runtime listens for JMX/RMI connections. If the IP address is on the same as the tc Runtime instance, you can enter 127.0.0.1.

Protocols

Specifies a comma-separated list of enabled SSL/TLS protocols. If you do not enter a value for this property, the default protocols are enabled.

Authenticate

Specifies whether tc Runtime authenticates users that connect to the server using the JMX port.

If you enable this field, tc Runtime looks up the user and password in the files specifies by the Access File and Password File fields, respectively; if tc Runtime finds the username and password in the files, then the user is authenticated and allowed JMX access. If you disable this property, all users may access tc Runtime via JMX.

You configure the JMX user and password in Hyperic on server instances the Inventory > Configuration Properties page. The default JMX user and password is configured by default when you install tc Server; if, however, you change the name or password of the user in the access and password files, you must also change the configured user/password in the Hyperic user interface.

Access File

Specifies the full pathname of the tc Runtime file that contains the list of users allowed to access tc Runtime using JMX. Note that this file is on the computer that hosts the tc Runtime instance, not the computer that hosts the Hyperic Server.

The access file contains one line per user; each line contains a username and permission level:

  • "readonly" - user can only view tc Runtime configuration

  • "readwrite" - user can view and modify tc Runtime configuration.
    The default name for the access file is jmxremote.access; the default location is the CATALINA_BASE/conf directory of the tc Runtime instance. Each tc Runtime instance is configured by default with an "admin" user with readwrite permission.

Password File

Specifies the full pathname of the tc Runtime file that contains passwords for the users listed in the Access File. Note that this file is on the computer that hosts the tc Runtime instance, not the computer that hosts the Hyperic Server.

The password file contains one line for each user listed in the access file; each line contains a username and password.

The default name for the password file is jmxremote.password; the default location is the CATALINA_BASE/conf directory of the tc Runtime instance. The password for the pre-configured  "admin" user is "springsource".

Use SSL

Specifies whether to use secure sockets layer (SSL) for users' JMX connections to tc Runtime.

To use SSL, you must first set up a digital certificate on the computer that hosts the tc Runtime instance and then configure the SSL setings on this page. You can use the command-line utility keytool (http://download.oracle.com/javase/1.4.2/docs/tooldocs/solaris/keytool.html) to manage digital certificates.

Client Authentication

Specifies whether client authentication is required when using SSL.

If you enable this property, tc Runtime authenticates JMX/SSL clients using certificate authentication rather than file-based authentication; this means that tc Runtime must find the client's certificate in its truststore or it will deny the client JMX access. This implies that only clients with known SSL certificates are allowed access to tc Runtime.

Use JDK Client Factory

Specifies whether or not the Hyperic Agent uses the required client libraries from the JDK. The required libraries are used to pass SSL-specific properties (such as the trust store and password) to the tc Runtime instance. If you disable this property, you must manually set up the Hyperic Agent's CLASSPATH to find these client libraries.

Cipher Suites

Specifies a comma-separated list of enabled SSL/TLS cipher suites. A cipher suite is a combination of cryptographic parameters that define the security algorithms and key sizes used for authentication, key agreement, encryption, and integrity protection.

If you do not enter a value for this property, the default cipher suites are enabled.

Truststore File

Specifies the full pathname of the truststore file used by SSL.

A truststore is a special kind of keystore file that is used when making decisions about what to trust. If you receive some data from an entity that you already trust, and if you can verify that the entity is the one it claims to be, then you can assume that the data came from that entity. This means that the key of a truststore file typically contains an entity's identity and a public key, as opposed to a private key contained in a more restricted keystore file.

Truststore Pass

Specifies the password used to access the truststore file.

Keystore File

Specifies the full pathname of the keystore file.

A keystore is a database of key material. Key material is used for a variety of purposes, including authentication and data integrity. There are various types of keystores available, including "PKCS12" and Sun's "JKS." Typically, the key of a keystore consists of an entity's identity and its private key.

Keystore Pass

Specifies the password used to access the keystore file.

Server Start Configuration

NOTE: Hyperic populates these fields with information contained in the CATALINA_HOME/bin/setenv.sh file of the tc Runtime instance you are configuring, specifically argument values defined in the JVM_OPTS environment variable.

If for some reason setenv.sh does not exist, or does not define JVM_OPTS, the Server Start fields will be blank.

Edits you make to Server Start fields in the Hyperic user interface are written back to setenv.sh.

General

Field Name

Description

Java Home

Specifies the full pathname to the JDK or JRE used by the tc Runtime instance.

Use Server HotSpot VM

Check to use the Java HotSpot Virtual Machine.

Min Heap Size

Specifies the initial size, in MB, of the memory allocation pool.

Max Heap Size

Specifies the maximum size, in MB, of the memory allocation pool.

Thread Stack Size

Specifies the amount of memory, in KB, allocated to a single JVM thread.

Sun Specific JVM Options

The options in the following table are specific to Sun JVMs.  Modify the option values with caution. If you use a non-Sun VM, altering the values might have unintended side effects.

Memory

Field Name

Description

Min Young Generation Size

Specifies the default size, in MB, of new generation.

Max Young Generation Size

Specifies the maximum size, in MB, of new generation. 

Min Perm Gen Size

Specifies the initial size, in MB, of the permanent generation. 

Max Perm Gen Size

Specifies the maximum size, in MB, of the permanent generation.

Garbage Collection

Field Name

Description

Max GC Pause

Sends a hint to the virtual machine that pause times of the specified milliseconds or less are desired. The VM will adjust the Java heap size and other GC-related parameters in an attempt to keep GC-induced pauses shorter than the specified value.

Note that this may cause the VM to reduce overall throughput, and in some cases the VM will not be able to meet the desired pause time goal.

Max GC Minor Pause

Similar to Max GC Pause, but for minor pauses.

Debug

Field Name

Description

Heap Dump on Out of Memory Error

Directs the JVM to generate a heap dump when an allocation from the Java heap or the permanent generation cannot be satisfied.

Print Message at GC

Specifies whether the JVM should print messages to the GC log file every time it performs a garbage collection.

Print Heap at GC

Specifies whether the JVM should print detailed information, including heap occupancy before and after a garbage collection, to the GC log file.

Print GC Application Stopped Time

Specifies whether the JVM should print the amount of time an application is stopped during a garbage collection to the GC log file.

Print GC Timestamps

Specifies whether the JVM should print timestamps relating to garbage collection to the GC log file.

Print GC Details

Specifies whether the JVM should print detailed information relating to garbage collection to the GC log file.

GC Log File

Specifies the name of the GC log file to which all garbage collection information is printed. Default value is CATALINA_BASE/logs/gc.log.

Advanced

Field Name

Description

Command Line Arguments

Enter additional options to the CATALINA_OPTS environment variables if they are not available as text fields on this  configuration page. Use one of these forms:

-XOptionValue

or

-XX:Option=Value

with a space between options.

For example:

-Xms512M -Xmx512M -XX:NewSize=128M

Server Defaults - JSP


The fields described in the following table configure JSP-related init params for every Web application deployed to this tc Runtime instance. Hyperic loads and updates the values from the CATALINA_BASE/conf/web.xml file for this tc Runtime instance.

Field Name

Description

Recompile Check Interval (s)

Specifies the interval, in seconds, at which tc Runtime checks to see if a JSP and its dependent file need to be recompiled. Default value is 0.
If you set this field to a value greater than zero, and Development Mode is unchecked, then tc Runtime performs the compilation in the background.

Development Mode

Specifies that tc Runtime is working in development mode. When this value is checked, you can specify the frequency at which JSPs are checked for modification using the Modification Test Interval field.

Modification Test Interval (s)

Specifies the interval, in seconds, that tc Runtime should wait before checking JSPs and their dependent files for modifications. If you set this field to 0, then tc Runtime checks the JSPs every time they are accessed. Default value is 4 seconds.

This feature is enabled only when Development Mode is checked.

Compiler

Specifies the JSPs compiler used by tc Runtime. If not set, then tc Runtime uses the default Eclipse JDT Java compiler.

Compiler Target VM

Specifies the JDK version with which the generated files are compatible. Default value is JDK 1.4.

Compiler Source VM

Specifies the JDK version with which the source files are compatible. Default value is JDK 1.4

Compile Class With Debug Information

Specifies whether the JSP class should be compiled with debug information.

Classpath

Specifies the CLASSPATH that tc Runtime should use when compiling the generated servlets. tc Runtime creates the default CLASSPATH dynamically based on the current Web application.

Fork JSP Page Compile to Separate JVM

Specifies whether tc Runtime should fork the compilation of JSPs so they are performed in a separate JVM than tc Runtime .

Enable Tag Handler Pooling

Enables tag handler pooling.

Internet Explorer class-id for <jsp:plugin> Tags

Specifies the class-id value that tc Runtime sends to Internet Explorer when using the tags.

Default value is clsid:8AD9C840-044E-11D1-B3E9-00805F499D93.

Java File Encoding

Specifies the Java file encoding to use for generating Java source files. Default value is UTF8.

Keep Generated Source Code

Specifies whether tc Runtime should keep the generated source code for each page rather than deleting it.

Generate One Print Statement Per Input Line

Specifies whether tc Runtime should generate static content with one print statement per input line, to ease debugging.

Trim Spaces In Template Text

Specifies whether tc Runtime should trim white spaces in template text between actions or directives. 

Suppress SMAP Information

Specifies whether tc Runtime should suppress the generation of SMAP information for JSR-45 debugging.

Dump SMAP Information

Specifies whether tc Runtime should dump SMAP information for JSR-45 debugging to a file. If you want to set this field to true (checked), then be sure to also uncheck Suppress SMAP Information.

Generate Strings as Char Arrays

Specifies whether strings should be generated as character arrays. Checking this field will sometimes increase the performance of JSPs.

Issue Error For Invalid useBean Class Attribute

Specifies whether tc Runtime should issue an error when the value of the class attribute in a useBean action is not a valid bean class.

Scratch Directory

Specifies the scratch directory that tc Runtime should use when compiling JSP pages. Default value is the work directory for the current Web application.

Add X-Powered-By Response Header

Specifies whether generated servlet adds the the X-Powered-By response header.

Server Defaults - Static Content


The fields described in the following table configure static content-related init params for every Web application deployed to this tc Runtime instance. Hyperic loads and updates the values from the CATALINA_BASE/conf/web.xml file for this tc Runtime instance.

Field Name

Description

Debug Level

Specifies the level of detail contained in the debugging messages from the current servlet. Default value is 0 (no debugging.)

File Encoding

Specifies the encoding that tc Runtime uses when reading static resources. The default value is the same as the file encoding of the platform on which tc Runtime is running.

Input Buffer Size

Specifies the size, in bytes, of the input buffer that tc Runtime uses when reading resources to be served. Default value is 2048.

Output Buffer Size

Specifies the size, in bytes, of the output buffer that tc Runtime uses when writing resources to be served. Default value is 2048.

Min Sendfile Size

Specifies the minimal file size, in KB, that tc Runtime uses with "sendfile". This field only works if the connector supports sendfile. Default value is 48.

Show Directory Listings

Specifies whether tc Runtime should produce a directory listing if there is no welcome file in the directory. WARNING: Directory listings that include many entries can be slow and consume significant proportion of the tc Runtime resources.

Readme File Name

File name to display with the directory contents. No default value.

Read Only

Specifies whether the current context is read-only, which means that it rejects HTTP commands such as PUT and DELETE.

tc Runtime JDBC Reference

This page provides reference information about the fields on the Views > Server Configuration > Resources tab used to configure and create JDBC data sources.

SpringSource tc Runtime provides two types of JDBC datasources: the standard DBCP one and a Tomcat datasource for highly-concurrent environments. For additional information about the two types of datasources, see Configuring and Creating JDBC Data Sources.

General Properties

Field Name

Description

JNDI Name

The JNDI path to which this data source is bound. By default, the JNDI name is the name of the data source.

Connection Properties

Field Name

Description

Username

The username that the JDBC driver uses to establish a connection to the database server.

Password

The password that the JDBC driver uses to establish a connection to the database server.

URL

The connection URL that the JDBC driver uses to establish a connection to the database server. This URL varies for each type of database driver. An example for the MySQL database is:

jdbc:mysql://localhost:3306/javatest?autoReconnect=true

Driver Class Name

The fully qualified name of the JDBC driver class used to create the physical database connections in the connection pool. The driver class name varies for the type of JDBC driver. An example of the driver class name for connecting to a MySQL database server is:

com.mysql.jdbc.Driver.

Connection Properties

The connection properties that tc Runtime sends to the JDBC driver when establishing new connections. Format of the string must be [propertyName=property;]

NOTE - tc Runtime passes the "user" and "password" properties explicitly, so do not include them in this field.

Tomcat/DBCP Connection Pool Properties

Field Name

Description

Default Auto Commit

Specifies whether connections created by this pool are by default in an auto-commit state. 

Default Read Only

Specifies whether connections created by this pool are by default read only. 

Default Transaction Isolation

Specifies the default transation isolation state for connections created by this pool. Values can be:

  • NONE: Transactions are not supported.

  • READ_COMMITTED: Dirty reads are prevented; non-repeatable reads and phantom reads can occur.

  • READ_UNCOMMITTED: Dirty reads, non-repeatable reads and phantom reads can occur.

  • REPEATABLE_READ: Dirty reads and non-repeatable reads are prevented; phantom reads can occur.

  • SERIALIZABLE: Dirty reads, non-repeatable reads and phantom reads are prevented. Default value depends on the database driver.

Default Catalog

Specifies the default catalog of connections created by this pool.

Initial Number of Connections

Specifies the initial number of connections that are created when tc Runtime starts this connection pool. Default value is 0 (DBCP datasource) or 10 (Tomcat datasource).

Max Active Connections

Specifies the maximum number of active connections that tc Runtime can allocate from this pool at the same time. Specify a negative number for no limit. Default value is 8 (DBCP datasource) or 100 (Tomcat datasource).

Max Idle Connections

Specifies the maximum number of connections that can remain idle in the pool without any extra ones being released. Specify a negative number for no limit. Default value is 8 (DBCP datasource) or 100 (Tomcat datasource).

Min Idle Connections

Specifies the minimum number of connections that can remain idle in the pool without any extra ones being created. Specify 0 to create none. Default value is 0 (DBCP datasource) or 10 (Tomcat datasource).

Max Wait Time For Connection Borrow

The maximum number of milliseconds that the connection pool waits (when there are no available connections) for a connection to be returned before throwing an exception. Specify -1 to wait indefinitely. Default value is -1 (DBCP datasource) or 30000 (Tomcat datasource).

Validation Query

The SQL query that the driver uses to validate connections from this pool before returning them to the caller. If specified, this query MUST be an SQL SELECT statement that returns at least one row.

Test on Borrow

Specifies whether tc Runtime validates objects before being borrowed from the pool. If the object fails to validate, tc Runtime drops it from the pool and attempts to borrow another.

NOTE - for a value in this field to have any effect, you must set the Validation Query field to a non-null string.

Test on Return

Specifies whether tc Runtime validates objects before returning them to the connection pool. 

Test While Idle

Specifies whether the idle object evictor validates objects. If an object fails to validate, tc Runtime drops it from the connection pool.

NOTE - for a value in this field to have any effect, you must set the Validation Query field to a non-null string.

Time Between Eviction Runs

The number of milliseconds to sleep between runs of the idle object evictor thread. When non-positive, tc Runtime does not run an idle object evictor thread. Default value is -1 (DBCP datasource) or 5000 (Tomcat datasource).

Test Per Eviction Runs

The number of objects to examine during each run of the idle object evictor thread (if any). Default value is 3. 

Min Evictable Idle Time

The minimum amount of time, in milliseconds, that an object may sit idle in the pool before it is eligable for eviction by the idle object evictor (if any).

Pool Prepared Statements

Enables prepared statement pooling for this connection pool.

Max Opened Prepared Statements

The maximum number of open statements that can be allocated from the statement pool at the same time. Set this field to 0 for no limit. Default value is 0.

Allow Access to Underlying Connection

Specifies whether the PoolGuard allows access to the underlying connection. 

Remove Abandoned Connections

Specifies whether tc Runtime should remove abandoned connections if they exceed the value of the Remove Abandoned Timeouts field. If checked, a connection is considered abandoned and eligible for removal if it has been idle longer than the value of Remove Abandoned Timeouts. Checking this field can recover database connections from poorly written applications which fail to close a connection.

Remove Abandoned Timeouts

Specifies the amount of time, in seconds, before tc Runtime can remove an abandoned connection. Default value is 300 seconds.

Log Abandoned Statements and Connections

Specifies whether tc Runtime should log stack traces for application code that abandoned a Statement or Connection.

NOTE: Logging of abandoned Statements and Connections adds overhead for every Connection open or new Statement because a stack trace has to be generated.

Validation Interval (ms)

Tomcat datasource only. Specifies the time, in milliseconds, that tc Runtime waits before running a validation check to ensure that the JDBC connection is still valid. Too frequent validation checks can slow performance. Default value for this field is 30000 (30 seconds).

Fair Queue

Tomcat datasource only. Specifies that calls to getConnection() should be treated fairly in a true FIFO (first in, first out) fashion. You are required to enable this feature if you want to use the asynchronous connection retrieval feature, which is the ability to queue your connection request.

JMX Enabled

Tomcat datasource only. Specifies whether the connection pool is registered with the JMX server.

Use equals comparison

Tomcat datasource only. Specifies whether the ProxyConnection class should use String.equals() instead of == when comparing method names. Does not apply to added interceptors as those are configured individually.

Init SQL

Tomcat datasource only. Specifies an initial SQL statement that is run only when a connection is first created. You can use this featuer to setup session settings that you want to exist during the entire time the connection is established.

JDBC Interceptors

Tomcat datasource only. Semi-colon separated list of classnames that tc Runtime inserts as interceptors in the chain of operations on the java.sql.Connection object. The interceptor classes must extend the abstract class:

org.apache.tomcat.jdbc.pool.JdbcInterceptor

SpringSource tc Runtime provides a JDBC Interceptor called SlowQueryReportJmx that keeps a report of slow JDBC queries, or JDBC queries that did not complete below a configured time threshold. If you want AMS to display this report in its Console, then you must add the SlowQueryReportJmx interceptor to this text field. For example, to add it to the default interceptors, enter this value:

ConnectionState;StatementFinalizer;SlowQueryReportJmx

The default threshold for the SlowQueryReportJmx interceptor is 5000 milliseconds. If you want to change the default value, include it as a parameter to the interceptor, as shown:

ConnectionState;StatementFinalizer;SlowQueryReportJmx(threshold=6000)
After you have configured the SlowQueryReportJmx interceptor, AMS creates and auto-discovers a service called "JDBC Query Report" that contains information about slow JDBC queries.

Service Configuration Reference

tc Runtime Services Reference

This section defines the fields on the Views > Server Configuration > Services tab used to configure and create tc Runtime services.

A tc Runtime service represents the combination of one or more Connector components that share a single Engine component for processing incoming requests. A tc Runtime consists of one or more services. The default tc Runtime service which is always present in newly created tc Runtime instance is called "catalina."

See The Service Component on the Apache Web site for more information.

General Service Properties

Field Name

 Description

Name

Specifies the name of this tc Runtime service. Within the scope of a tc Runtime , the service name must be unique. This is the name that appears in the tc Runtime log messages.

Connector Properties

Each tc Runtime service can have one or more connectors configured. Connectors are specific to a protocol, such as HTTP or AJP. See the following documentation on the Apache Web site for additional detailed information:

General

Field Name

Description

Protocol

Specifies the protocol that handles incoming and outgoing messages for this connector. This field can have the following values:

  • org.apache.coyote.http11.Http11Protocol (same as HTTP/1.1). This is the default value. Note that if you want to use HTTPS, you do not specify "HTTPS/1.1", but rather, set the "secure" field to true.

  • org.apache.coyote.http11.Http11NioProtocol - non blocking Java connector

  • org.apache.coyote.http11.Http11AprProtocol - the APR connector.

IP Address

For tc Runtime instances with more than one IP address, this attribute identifies a single address, upon which the listen port defined in the Port attribute will be opened for connections.  If a specific IP address is not specified, server sockets will be created on all IP addresses associated for the server, on the port specified in the Port attribute. 

Port

Specifies the TCP port number on which this connector will create a server socket and await incoming connections. Your operating system allows only one server application to listen to a particular port number on a particular IP address, which means that multiple tc Runtime instances running on the same computer must have unique ports. Default value is 8080.

Accept Count

HTTP(S) Connectors only. Specifies maximum queue length for incoming connection requests when all possible request processing threads are in use. Any requests received when the queue is full will be refused. The default value is 10.

Max Keep Alive Requests

HTTP(S) Connectors only. Specifies the maximum number of HTTP requests that can be pipelined until the connection is closed by the server. A value of 1 disables HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelining. A value of -1 allows an unlimited amount of pipelined or keep-alive HTTP requests. The default value of this field is 100.

Proxy Host

If this connector is being used in a proxy configuration, specifies the server name that is returned from calls to request.getServerName(). See Proxy Support HOW-TOP for more information.

Proxy Port

If this connector is being used in a proxy configuration, specifies the server port that is returned from calls to request.getServerPort(). See Proxy Support HOW-TOP for more information.

Redirect Port

Specifies the port to which a user is redirected if they require a secure connection. If this connector supports non-SSL requests, and a request is received for which a matching requires SSL transport, tc Runtime automatically redirects the request to the port number specified here.

Scheme

Specifies the name of the protocol you want to have returned by calls to request.getScheme(). For example, set this field to "https" for an SSL Connector. The default value is "http".

Connection Timeout

Specifies the number of milliseconds this connector waits, after accepting a connection, for the request URI line to be presented. The default value is 60000 (i.e. 60 seconds).

Max Threads

Specifies the maximum number of request processing threads that this connector creates, which in turn determines the maximum number of simultaneous requests that can be handled. If an executor is associated with this connector, tc Runtime ignores this attribute as the connector will execute tasks using the executor rather than an internal thread pool. The default value of this field is 40.

Request Secret Keyword

Specifies that only requests from workers with this secret keyword will be accepted.

Use Request Secret Keyword

Specifies whether tc Runtime should generate a random value for the Request Secret Keyword field.

Security/SSL

Field Name

Description

Secure

Specifies whether you want user calls to request.isSecure() to return true for requests received by this connector. Check this field for connectors (both SSL and non-SSL) that receive data from an SSL accelerator, like a crypto card, a SSL appliance or even a Web server.

Enable SSL

Enables SSL traffic (handshake/encryption/decription) for this connector. When enabled, be sure to also set the "scheme" and "secure" attributes so that correct values are returned to user calls to request.getScheme() and request.isSecure(). See SSL Support for more information. 

Certificate Encoding Algorithm

Specifies the certificate encoding algorithm. The default value is the Sun implementation (SunX509). For IBM JVMs use the value IbmX509. For other vendors, consult the JVM documentation for the correct value.

Keystore File

Specifies the pathname of the keystore file that contains the server certificate to be loaded. By default, the pathname is the file ".keystore" in the operating system home directory of the user that starts the tc Runtime instance.

Keystore Password

Specifies the password used to access the server certificate from the specified keystore file. The default value is "changeit".

Key Alias

Specifies the alias that tc Runtime uses when accessing the server certificate in the keystore. If not specified, tc Runtime uses the first key read in the keystore.

APR SSL Settings

These settings are only relevant for APR based connectors that also use SSL.

Field Name

Description

SSL Protocol

Specifies the protocol that tc Runtime might use to communicate with clients. Valid values are "SSLv2", "SSLv3", "TLSv1", and "SSLv2+SSLv3". Default value is "all".

SSL Cipher Suite

Specifies the ciphers that tc Runtime might use to communicate with clients. Valid values is a list of ciphers, separated by a colon.

Default value is "all". See the OpenSSL Web site for the list of valid ciphers. 

SSL Certificate File

Specifies the name of the file that contains the server certificate. The format is PEM-encoded.

SSL Certificate Key File

Specifies the name of the file that contains the server private key. The format is PEM-encoded. The default value is the value of the SSL Certificate File field, which implies that both the certificate and the private key are in the same file. For security reasons, this is not recommended.

SSL Password

Specifies the password for the encrypted private key. If this field is left blank, the callback function prompts for the password.

SSL Verify Client

Specifies whether tc Runtime should ask client for certificate. The default value is "none", which means that the client will not have the opportunity to submit a certificate. Other valid values include "optional", "require" and "optionalNoCA".

SSL Verify Depth

Specifies the maximum verification depth for client certificates. The default value is "10". 

SSL CA Certificate File

Specifies the single file where you assemble the certificates of Certification Authorities (CA) for the clients that you authenticate. The file is the concatenation of the various PEM-encoded Certificate files, in order of preference. See Apache Module mod_ssl for more information. 

SSL CA Certificate Path

Specifies the directory where you keep the Certificates of Certification Authorities (CAs) for the clients that you authenticate. These are used to verify the client certificate on Client Authentication.
The files in this directory must be PEM-encoded and are accessed through hash filenames. So usually you can't just place the Certificate files there: you also have to create symbolic links named hash-value.N. And you should always make sure this directory contains the appropriate symbolic links. Use the Makefile which comes with mod_ssl to accomplish this task. See Apache Module mod_ssl for more information.

SSL Certificate Chain File

Specifies the optional all-in-one file where you can assemble the certificates of Certification Authorities (CA) which form the certificate chain of the server certificate. This starts with the issuing CA certificate of of the server certificate and can range up to the root CA certificate. Such a file is simply the concatenation of the various PEM-encoded CA Certificate files, usually in certificate chain order. See Apache Module mod_ssl for more information.

SSL CA Revocation File

Specifies the directory where you keep the Certificate Revocation Lists (CRL) of Certification Authorities (CAs) whose clients you deal with. These are used to revoke the client certificate on Client Authentication. See Apache Module mod_ssl for more information.

SSL CA Revocation Path

Specifies the directory where you keep the Certificate Revocation Lists (CRL) of Certification Authorities (CAs) whose clients you deal with. These are used to revoke the client certificate on Client Authentication. See Apache Module mod_ssl for more information.

Engine Properties

A tc Runtime engine represents the entire request processing machinery associated with a particular service. It receives and processes all requests from one or more connectors, and returns the completed response to the connector for ultimate transmission back to the client.

Each Service must be associated with exactly one engine.

Field Name

Description

Name

Specifies the name of this service. This is the name used in tc Runtime logging messages. Each service name must be unique within the scope of a tc Runtime instance.

Default Host

Specifies the default host name. This name corresponds to the name of a Host component that processes requests directed to host names on this server, but which are not explicitly configured for this tc Runtime instance.

JVM Route

Specifies the identifier that must be used in load balancing scenarios to enable session affinity. The identifier, which must be unique across all tc Runtime instances that participate in a cluster, is appended to the generated session identifier, therefore allowing the front end proxy to always forward a particular session to the same tc Runtime instance.

Thread Diagnostics

When you deploy and start a Web application on a tc Runtime instance, and then clients begin connecting and using the application, you might find that the clients occasionally run into problems such as slow requests or even failed requests. Although tc Runtime by default logs these errors in the log files, it is often difficult to pinpoint where exactly the error came from and how to go about fixing it. By enabling thread diagnostics, tc Runtime provides additional information to help you troubleshoot the problem.

A failed request is one that simply did not execute; a slow request is defined as a request that takes longer than the configured threshold. The default threshold is 500 milliseconds.

When you enable thread diagnostics, you can view the following contextual information about a slow or failed client request:

  • The time and date when the slow or failed request happened.

  • The exact URL invoked by the client that resulted in a slow or failed request.

  • The exact error returned by the request.

  • The database queries that were executed as part of the request and how long each one took.

  • Whether any database connection failed or succeeded.

  • Whether the database had any other connectivity problems.

  • Whether the database connection pool ran out of connections.

  • Whether any garbage collection occurred during the request, and if so, how long it took.

Field Name

Description

Enable Thread Diagnostics

Enables the gathering of thread diagnostic information

To view this information after you have enabled thread diagnostics, go to the Monitor tab of a particular tc Runtime instance, then click on the servername Thread Diagnostics link in the Resources > Services window on the left.

History

Specifies the maximum number of requests that have met the threshold condition that tc Runtime keeps as historical data. The default value is 1000. You can query this historical data using JMX; it is not presented in the HQ user interface.

Threshold

Specifies the threshold, in milliseconds, after which a client request is considered slow. The default value is 5000 milliseconds.

Host Properties

A tc Runtime Host represents a virtual host, which is an association of a network name for a tc Runtime (such as "www.mycompany.com" associated with the particular tc Runtime . To be effective, the network name must be registered in the Domain Name Service (DNS) server that manages the Internet domain to which you belong

A tc Runtime engine must be associated with one or more hosts. One of the hosts must be the default host, or the one pointed to by the "Default Host" field of the Engine configuration.

Field Name

Description

Name

Specifies the network name of this virtual host, as registered in your Domain Name Service (DNS) server. One of the Hosts associated within a tc Runtime engine MUST have a name that matches the "Default Host" setting for that engine. See Host Name Aliases for information on how to assign more than one network name to the same virtual host.

Application Base Directory

Specifies the application base directory for this virtual host. The application base directory may contain Web applications to be deployed on this virtual host. You can specify an absolute pathname for this directory, or a pathname that is relative to the $CATALINA_BASE directory. See Automatic Application Deployment for more information on automatic recognition and deployment of Web applications.

Auto Deploy Web Applications

Specifies whether new Web applications that are copied to the application base directory while tc Runtime is running should be automatically deployed. See Automatic Application Deployment for more information. 

Deploy Applications on Startup

Specifies whether Web applications from this host should be automatically deployed when the tc Runtime instance starts up. See Automatic Application Deployment for more information.

Unpack WARs

Specifies whether tc Runtime should unpack Web applications that are copied to the application base directory as Web application archive (WAR) files into a corresponding disk directory structure. If unchecked, tc Runtime runs the Web applications directory from a WAR file. See Automatic Application Deployment

for more information. 

Deploy XML

Specifies whether tc Runtime should parse the "context.xml" file embedded inside the Web application (located at /META-INF/context.xml). Security consious environments should set this to false (uncheck) to prevent applications from interacting with the container's configuration. The administrator will then be responsible for providing an external context configuration file, and put it in $CATALINA_BASE/conf/enginename/hostname/.

Work Directory

Specifies the pathname to a scratch directory used by applications for this Host. Each application will have its own sub directory with temporary read-write use. Configuring a Context work directory overrides use of the Host work directory configuration. This directory will be made visible to servlets in the Web application by a servlet context attribute (of type java.io.File) named javax.servlet.context.tempdir as described in the Servlet Specification. If not specified, a suitable directory underneath $CATALINA_BASE/work will be provided.

HTTP Access Logging

The tc Runtime logging subsystem creates log files in the same format as those created by standard Web servers. These logs can later be analyzed by standard log analysis tools to track page hit counts, user session activity, and so on. The logging files are rolled over nightly at midnight.

Field Name

Description

Enable Logging

Specifies whether you want to enable logging on this engine or virtual host.

Directory

Specifies the absolute or relative pathname of a directory in which tc Runtime creates the log files log files. If you specify a relative pathname, it is relative to $CATALINA_BASE. The default value is $CATALINA_BASE/logs.

Pattern

A formatting layout identifying the various information fields from the request and response to be logged, or the word "common" or "combined" to select a standard format. See the Apache Web site for more information on configuring this attribute. Note that the optimized access does only support "common" and "combined" as the value for this attribute.

File Name Prefix

Specifies the prefix added to the start of each log file's name. The default value is "access_log." Leave the field blank if you do not want a prefix.

File Name Suffix

Specifies the suffix added to the end of each log file's name. Leave the field blank if you do not want a suffix (default behavior).

File Date Format

Specifies a customized date format in the access log file name. The date format also specifies how often the file is rotated. For example, if you want the log files to rotate every hour, then set this value to: yyyy-MM-dd.HH

Metrics

tc Runtime 6.0

SpringSource tc Runtime 6.0 Web Module Stats service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: stop,start,reload
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Processing Time

processingTime

sec

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 6.0 Tomcat JDBC Connection Pool Global service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 Tomcat JDBC Connection Pool Context service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 Thread Pools service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported:

Name

Description

maxThreads

Maximum Number of Threads

Supported Control Actions: start,shutdown
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Current Thread Count

currentThreadCount

none

UTILIZATION

true

5 min

Current Thread Busy

currentThreadsBusy

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 6.0 Thread Diagnostics Host service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 Thread Diagnostics Engine service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 Thread Diagnostics Context service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 Servlet Monitor service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Class Load Time

classLoadTime

none

UTILIZATION

false

5 min

Error Count

errorCount

none

UTILIZATION

false

10 min

Error Count per Minute

errorCount1m

none

UTILIZATION

true

10 min

Load Time

loadTime

none

UTILIZATION

false

5 min

Processing Time

processingTime

none

UTILIZATION

false

10 min

Processing Time per Minute

processingTime1m

none

UTILIZATION

false

10 min

Request Count

requestCount

none

UTILIZATION

false

10 min

Request Count per Minute

requestCount1m

none

UTILIZATION

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 server

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: start,stop,restart
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

UpTime

Uptime

ms

UTILIZATION

true

30 min

Thread Count

ThreadCount

none

UTILIZATION

false

10 min

Thread Count per Minute

ThreadCount1m

none

UTILIZATION

false

10 min

Current Thread Cpu Time

CurrentThreadCpuTime

ms

UTILIZATION

false

10 min

Current Thread Cpu Time per Minute

CurrentThreadCpuTime1m

ms

UTILIZATION

false

10 min

Current Thread User Time

CurrentThreadUserTime

ms

UTILIZATION

false

10 min

Current Thread User Time per Minute

CurrentThreadUserTime1m

ms

UTILIZATION

false

10 min

Daemon Thread Count

DaemonThreadCount

none

UTILIZATION

false

5 min

Peak Thread Count

PeakThreadCount

none

UTILIZATION

false

30 min

Free Swap Space Size

FreeSwapSpaceSize

B

UTILIZATION

false

5 min

Free Physical Memory Size

FreePhysicalMemorySize

B

UTILIZATION

false

5 min

Process Cpu Time

ProcessCpuTime

ns

UTILIZATION

false

10 min

Process Cpu Time per Minute

ProcessCpuTime1m

ns

UTILIZATION

false

10 min

Open File Descriptor Count

OpenFileDescriptorCount

none

UTILIZATION

false

5 min

Heap Memory Used

HeapMemoryUsed

B

UTILIZATION

true

5 min

Heap Memory Committed

HeapMemoryCommitted

B

UTILIZATION

true

5 min

Heap Memory Max

HeapMemoryMax

B

UTILIZATION

true

30 min

Heap Memory Free

HeapMemoryFree

B

UTILIZATION

true

5 min

Deadlocks Detected

DeadlocksDetected

none

UTILIZATION

true

2 min

Availability

Availability

percentage

AVAILABILITY

true

5 min

Percent Up Time in Garbage Collection

PercentUpTimeinGarbageCollection

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 6.0 JSP Monitor service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

JSP Count

jspCount

none

UTILIZATION

false

10 min

JSP Count per Minute

jspCount1m

none

UTILIZATION

true

10 min

JSP Reload Count

jspReloadCount

none

UTILIZATION

false

10 min

JSP Reload Count per Minute

jspReloadCount1m

none

UTILIZATION

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 Java Process Metrics service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Process Virtual Memory Size

ProcessVirtualMemorySize

B

UTILIZATION

false

5 min

Process Resident Memory Size

ProcessResidentMemorySize

B

UTILIZATION

true

5 min

Process Page Faults

ProcessPageFaults

none

UTILIZATION

false

10 min

Process Page Faults per Minute

ProcessPageFaults1m

none

UTILIZATION

false

10 min

Process Cpu System Time

ProcessCpuSystemTime

ms

UTILIZATION

false

10 min

Process Cpu System Time per Minute

ProcessCpuSystemTime1m

ms

UTILIZATION

false

10 min

Process Cpu User Time

ProcessCpuUserTime

ms

UTILIZATION

false

10 min

Process Cpu User Time per Minute

ProcessCpuUserTime1m

ms

UTILIZATION

false

10 min

Process Cpu Total Time

ProcessCpuTotalTime

ms

UTILIZATION

false

10 min

Process Cpu Total Time per Minute

ProcessCpuTotalTime1m

ms

UTILIZATION

false

10 min

Process Cpu Usage

ProcessCpuUsage

percentage

UTILIZATION

true

5 min

Process Start Time

ProcessStartTime

epoch-millis

AVAILABILITY

false

10 min

Process Open File Descriptors

ProcessOpenFileDescriptors

none

UTILIZATION

false

5 min

Process Threads

ProcessThreads

none

UTILIZATION

false

5 min

Child Processes

ChildProcesses

none

UTILIZATION

false

5 min

Configuration help:

SpringSource tc Runtime 6.0 HTTP service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Inbound Connections

InboundConnections

none

UTILIZATION

true

5 min

Outbound Connections

OutboundConnections

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 6.0 Global Request Processor service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Bytes Sent

bytesSent

none

UTILIZATION

false

10 min

Bytes Sent per Minute

bytesSent1m

none

UTILIZATION

false

10 min

Bytes Received

bytesReceived

none

UTILIZATION

false

10 min

Bytes Received per Minute

bytesReceived1m

none

UTILIZATION

false

10 min

Error Count

errorCount

none

UTILIZATION

false

10 min

Error Count per Minute

errorCount1m

none

UTILIZATION

true

10 min

Processing Time

processingTime

none

UTILIZATION

false

10 min

Processing Time per Minute

processingTime1m

none

UTILIZATION

true

10 min

Request Count

requestCount

none

UTILIZATION

false

10 min

Request Count per Minute

requestCount1m

none

UTILIZATION

true

10 min

Configuration help:

SpringSource tc Runtime 6.0 Garbage Collector service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Collection Count

CollectionCount

none

THROUGHPUT

false

10 min

Collection Count per Minute

CollectionCount1m

none

THROUGHPUT

false

10 min

Collection Time

CollectionTime

none

THROUGHPUT

false

10 min

Collection Time per Minute

CollectionTime1m

none

THROUGHPUT

false

10 min

Configuration help:

SpringSource tc Runtime 6.0 Executor service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Max Threads

maxThreads

none

UTILIZATION

true

5 min

Pool Size

poolSize

none

UTILIZATION

true

5 min

Active Count

activeCount

none

UTILIZATION

true

5 min

Queue Size

queueSize

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 6.0 Data Source Global service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported:

Name

Description

initialSize

Initial Size

maxActive

Maximum Active Connections

minIdle

Minimum Idle Connections

maxIdle

Maximum Idle Connections

url

JDBC URL

username

Username

Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Current Number of Active Connections

numActive

none

UTILIZATION

true

5 min

Current Number of Idle Connections

numIdle

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 6.0 Data Source Context service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported:

Name

Description

initialSize

Initial Size

maxActive

Maximum Active Connections

minIdle

Minimum Idle Connections

maxIdle

Maximum Idle Connections

url

JDBC URL

username

Username

Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Current Number of Active Connections

numActive

none

UTILIZATION

true

5 min

Current Number of Idle Connections

numIdle

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 6.0 Cache service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Access Count

accessCount

none

UTILIZATION

false

10 min

Access Count per Minute

accessCount1m

none

UTILIZATION

true

10 min

Hits Count

hitsCount

none

UTILIZATION

false

10 min

Hits Count per Minute

hitsCount1m

none

UTILIZATION

true

10 min

Configuration help:

tc Runtime 7.0

SpringSource tc Runtime 7.0 Web Module Stats service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: stop,start,reload
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Processing Time

processingTime

sec

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 7.0 Tomcat JDBC Connection Pool Global service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 Tomcat JDBC Connection Pool Context service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 Thread Pools service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported:

Name

Description

maxThreads

Maximum Number of Threads

Supported Control Actions: start,shutdown
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Current Thread Count

currentThreadCount

none

UTILIZATION

true

5 min

Current Thread Busy

currentThreadsBusy

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 7.0 Thread Diagnostics Host service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 Thread Diagnostics Engine service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 Thread Diagnostics Context service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 Servlet Monitor service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Class Load Time

classLoadTime

none

UTILIZATION

false

5 min

Error Count

errorCount

none

UTILIZATION

false

10 min

Error Count per Minute

errorCount1m

none

UTILIZATION

true

10 min

Load Time

loadTime

none

UTILIZATION

false

5 min

Processing Time

processingTime

none

UTILIZATION

false

10 min

Processing Time per Minute

processingTime1m

none

UTILIZATION

false

10 min

Request Count

requestCount

none

UTILIZATION

false

10 min

Request Count per Minute

requestCount1m

none

UTILIZATION

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 server

Log Track Supported: Yes
Config Track Supported: Yes
Custom Properties Supported: None
Supported Control Actions: start,stop,restart
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

UpTime

Uptime

ms

UTILIZATION

true

30 min

Thread Count

ThreadCount

none

UTILIZATION

false

10 min

Thread Count per Minute

ThreadCount1m

none

UTILIZATION

false

10 min

Current Thread Cpu Time

CurrentThreadCpuTime

ms

UTILIZATION

false

10 min

Current Thread Cpu Time per Minute

CurrentThreadCpuTime1m

ms

UTILIZATION

false

10 min

Current Thread User Time

CurrentThreadUserTime

ms

UTILIZATION

false

10 min

Current Thread User Time per Minute

CurrentThreadUserTime1m

ms

UTILIZATION

false

10 min

Daemon Thread Count

DaemonThreadCount

none

UTILIZATION

false

5 min

Peak Thread Count

PeakThreadCount

none

UTILIZATION

false

30 min

Free Swap Space Size

FreeSwapSpaceSize

B

UTILIZATION

false

5 min

Free Physical Memory Size

FreePhysicalMemorySize

B

UTILIZATION

false

5 min

Process Cpu Time

ProcessCpuTime

ns

UTILIZATION

false

10 min

Process Cpu Time per Minute

ProcessCpuTime1m

ns

UTILIZATION

false

10 min

Open File Descriptor Count

OpenFileDescriptorCount

none

UTILIZATION

false

5 min

Heap Memory Used

HeapMemoryUsed

B

UTILIZATION

true

5 min

Heap Memory Committed

HeapMemoryCommitted

B

UTILIZATION

true

5 min

Heap Memory Max

HeapMemoryMax

B

UTILIZATION

true

30 min

Heap Memory Free

HeapMemoryFree

B

UTILIZATION

true

5 min

Deadlocks Detected

DeadlocksDetected

none

UTILIZATION

true

2 min

Availability

Availability

percentage

AVAILABILITY

true

5 min

Percent Up Time in Garbage Collection

PercentUpTimeinGarbageCollection

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 7.0 JSP Monitor service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

JSP Count

jspCount

none

UTILIZATION

false

10 min

JSP Count per Minute

jspCount1m

none

UTILIZATION

true

10 min

JSP Reload Count

jspReloadCount

none

UTILIZATION

false

10 min

JSP Reload Count per Minute

jspReloadCount1m

none

UTILIZATION

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 Java Process Metrics service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Process Virtual Memory Size

ProcessVirtualMemorySize

B

UTILIZATION

false

5 min

Process Resident Memory Size

ProcessResidentMemorySize

B

UTILIZATION

true

5 min

Process Page Faults

ProcessPageFaults

none

UTILIZATION

false

10 min

Process Page Faults per Minute

ProcessPageFaults1m

none

UTILIZATION

false

10 min

Process Cpu System Time

ProcessCpuSystemTime

ms

UTILIZATION

false

10 min

Process Cpu System Time per Minute

ProcessCpuSystemTime1m

ms

UTILIZATION

false

10 min

Process Cpu User Time

ProcessCpuUserTime

ms

UTILIZATION

false

10 min

Process Cpu User Time per Minute

ProcessCpuUserTime1m

ms

UTILIZATION

false

10 min

Process Cpu Total Time

ProcessCpuTotalTime

ms

UTILIZATION

false

10 min

Process Cpu Total Time per Minute

ProcessCpuTotalTime1m

ms

UTILIZATION

false

10 min

Process Cpu Usage

ProcessCpuUsage

percentage

UTILIZATION

true

5 min

Process Start Time

ProcessStartTime

epoch-millis

AVAILABILITY

false

10 min

Process Open File Descriptors

ProcessOpenFileDescriptors

none

UTILIZATION

false

5 min

Process Threads

ProcessThreads

none

UTILIZATION

false

5 min

Child Processes

ChildProcesses

none

UTILIZATION

false

5 min

Configuration help:

SpringSource tc Runtime 7.0 HTTP service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Inbound Connections

InboundConnections

none

UTILIZATION

true

5 min

Outbound Connections

OutboundConnections

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 7.0 Global Request Processor service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Bytes Sent

bytesSent

none

UTILIZATION

false

10 min

Bytes Sent per Minute

bytesSent1m

none

UTILIZATION

false

10 min

Bytes Received

bytesReceived

none

UTILIZATION

false

10 min

Bytes Received per Minute

bytesReceived1m

none

UTILIZATION

false

10 min

Error Count

errorCount

none

UTILIZATION

false

10 min

Error Count per Minute

errorCount1m

none

UTILIZATION

true

10 min

Processing Time

processingTime

none

UTILIZATION

false

10 min

Processing Time per Minute

processingTime1m

none

UTILIZATION

true

10 min

Request Count

requestCount

none

UTILIZATION

false

10 min

Request Count per Minute

requestCount1m

none

UTILIZATION

true

10 min

Configuration help:

SpringSource tc Runtime 7.0 Garbage Collector service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Collection Count

CollectionCount

none

THROUGHPUT

false

10 min

Collection Count per Minute

CollectionCount1m

none

THROUGHPUT

false

10 min

Collection Time

CollectionTime

none

THROUGHPUT

false

10 min

Collection Time per Minute

CollectionTime1m

none

THROUGHPUT

false

10 min

Configuration help:

SpringSource tc Runtime 7.0 Executor service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Max Threads

maxThreads

none

UTILIZATION

true

5 min

Pool Size

poolSize

none

UTILIZATION

true

5 min

Active Count

activeCount

none

UTILIZATION

true

5 min

Queue Size

queueSize

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 7.0 Data Source Global service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported:

Name

Description

initialSize

Initial Size

maxActive

Maximum Active Connections

minIdle

Minimum Idle Connections

maxIdle

Maximum Idle Connections

url

JDBC URL

username

Username

Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Current Number of Active Connections

numActive

none

UTILIZATION

true

5 min

Current Number of Idle Connections

numIdle

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 7.0 Data Source Context service

Log Track Supported: No
Config Track Supported: No
Custom Properties Supported:

Name

Description

initialSize

Initial Size

maxActive

Maximum Active Connections

minIdle

Minimum Idle Connections

maxIdle

Maximum Idle Connections

url

JDBC URL

username

Username

Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Current Number of Active Connections

numActive

none

UTILIZATION

true

5 min

Current Number of Idle Connections

numIdle

none

UTILIZATION

true

5 min

Configuration help:

SpringSource tc Runtime 7.0 Cache service

Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:

Name

Alias

Units

Category

Default On

Default Interval

Availability

Availability

percentage

AVAILABILITY

true

10 min

Access Count

accessCount

none

UTILIZATION

false

10 min

Access Count per Minute

accessCount1m

none

UTILIZATION

true

10 min

Hits Count

hitsCount

none

UTILIZATION

false

10 min

Hits Count per Minute

hitsCount1m

none

UTILIZATION

true

10 min

Configuration help:

Help us improve this information. Send feedback to docfeedback@vmware.com.
Created with Scroll Wiki EclipseHelp Exporter for Confluence.