Release notes
Release notes for the New Technology Agent Controller v4.1.0

1. General Notices
1.1 Supported Platforms
1.2 Multiple Instances of Agent Controller
1.3 Restricting Application Launch
1.4 Troubleshooting using the Agent Controller Log File
1.5 Using the SDK Package to Build Clients and Agents
2.  Known problems and limitations
2.1 Agent Controller
2.2 Client API
2.3 Compatibility
2.4 Documentation

  1. General Notices

References to "TPTP" should be read as equivalent to "Test and Performance Tools Platform".

Any references to "TPTP" in the documentation, installation, migration, or readme files should be read as equivalent to "Test and Performance Tools Platform".

1.1 Supported Platforms

Check here for information on the supported platforms.

1.2 Multiple Instances of Agent Controller

Multiple instances of the Agent Controller can run simultaneously if each is configured to use different communication channels. For more information, refer to the Connection TransportLayer  descriptions found in the Agent Controller configuration documentation.

1.3 Restricting Application Launch

By default, the Agent Controller will launch any application allowed by the system for the user that started the Agent Controller.  However, this can be restricted to only those applications listed in the Application Aliases list in the Agent Controller's serviceconfig.xml files by setting the launchAliasesOnly attribute to true. Refer to the Agent Controller configuration documentation for more information.

1.4 Troubleshooting using the Agent Controller Log File

The Agent Controller provides a logging service that allows agents to report errors, warnings, and debug messages into a log file common with itself. The amount of information and format of the logged messages is configured using the serviceconfig.xml file.  The DEBUG level setting results in significant output,  intended to assist in determining the source of problems.  The CBE logging format is intended for consumption by a CBE reader which allows filtering on the various fields, such as from which component a message originated.  The settings must be made prior to launching the Agent Controller.

By default, the log file, tptpAgentCtlr.log, is located in the same directory as the tptpAgentCtlr executable (i.e., <install-dir>/bin).  More information can be found in the Agent Controller configuration documentation.

1.5 Using the SDK Package to Build Clients and Agents

The SDK package provided on the download page for Linux (IA-32) can only be used when building clients and agents (including the samples) on Red Hat v7.2.  When running on any other IA-32 Linux OS distribution, you will need to get the source from CVS and rebuild from scratch.  Instructions for obtaining source and building it are found in the readme.txt file located in the <install-dir>/bin of the SDK package.


  1. Known Problems and Limitations

2.1 Agent Controller

Bugzilla defect: 110953

Cannot get notification of process termination for a process started outside the Agent Controller when running on Linux platforms.

Bugzilla defect: 114441

The Agent Controller's serviceconfig.xml specification for the agent it will use to launch processes (ProcessController) does not allow the executable to have command line arguments.

Bugzilla defect:104541

The Agent Controller does not broadcast events when agents register or deregister, or when they become available after having been in an unavailable state.

Bugzilla defect:117167

The readme.txt included with the Agent Controller packages refers to the old CVS root location when providing instructions on how to build from source.  The old root location is /home/tptp, it should be /cvsroot/tptp as the old name will eventually be deleted.

Bugzilla defect:117384

The Agent Controller will abort execution if the serviceconfig.xml file contains a blank line, space, or comment at the start of the file.  Workaround: Remove any whitespace or XML comment prior to the first “<” in the serviceconfig.xml file.

2.2 Client API

Bugzilla defect: 113421

Context values in a request command are intended to allow the client making a request to uniquely identify a response for that command.  However, it is possible for the Agent Controller or an agent to randomly choose the same value for its context in a message sent to the client that is not a response (e.g., when reporting a failure in some cases).

Bugzilla defect: 115002

When using the Java Client framework, a request to the Agent Controller  that expects a response will wait forever, (never timeout) if the Agent Controller or the agent to which the request was forwarded does not respond for any reason.

Bugzilla defect: 115003

The Java client framework prints the name of an Exception, but some exceptions have no specific message to describe the exception.

Bugzilla defect: 115665

Using the client framework's getAgentMetaData() method will cause the Agent Controller to abort .

Bugzilla defect: 117156

The client frameworks ProcessImpl::launch() method does not allow specification of append/prepend/replace options for command line arguments.  Nor does it build up any kind of environment variablies list for use in launching a application.

Bugzilla defect: 113597

The Java Agent API implementation does not support logging of error or debug messages into the Agent Controller's common log file as the C++ API implementation does.

Bugzilla defect: 113869

When compiling on new Linux distributions (RH EL4, SUSE 10), the Process Controller agent will abort while trying to register with the Agent Controller.  All other agents will as well.  The failure is caused by a difference in resolution of like-name functions, that should have been labeled static, but were not.  Workaround: Place the TPTPConfig library before the AgentBase library in the link specification.

Bugzilla defect: 115006

The Java Agent API implementation does not include processing command line arguments for the agent on startup as the C++ API implementation does.

Bugzilla defect:116457

The Java API is packaged with an out-dated version of Release Notes.  Refer to the new technology Agent Controller 4.1 documentation located on the consumer documents section of the TPTP documentation website for the most accurate information.

Bugzilla defect: 118935

Execution of a Java client application on Red Hat EL v3.0 requires the use of Sun Java 2 Standard Edition 1.4.2_07. Using a newer version of that SDK will result in a SAXParseException runtime error.

2.3 Compatibility

Bugzilla defect: 95546

Agent controller does not contain peer monitoring support.

Bugzilla defect: 112415

When an old agent attaches to the new Agent Controller through the compatibility transport layer, it isn't provided any configuration information.

2.4 Documentation

Bugzilla defect: 117607

There are 2 errors in the documentation for the Perfmon plugin migration sample.  Both are contained in the file index.html inside of  In Installation section 2.1, the instructions direct you to download the required Agent Controller from the "Technology Preview" section of the 4.1 download page.  The correct location is in the "New technology Agent Controller" section.   The second correction is in Figure 12 which depicts the selection of Agent Controllers that can be connected to.  The default port number shown is 10002, but it the actual default is 10006.  The port number must match that specified in the serviceconfig.xml file for the Agent Controller you wish to connect to. 

* Other brands and names are the property of their respective owners.

Copyright (C) 2005, Intel Corporation.

All rights reserved. This program and the accompanying materials
are made available under the terms of the Eclipse Public License v1.0
which is available at