Troubleshooting Passive Agents
Because passive agents must wait for a request from the JavaTest Harness harness before running tests, the port that the passive agent uses must be the same as that used by the JavaTest Harness harness to send requests.
Errors in configuring, synchronizing, or implementing the connection between the agent and the JavaTest Harness harness are the most probable causes of failure.
Use the Agent Monitor window, the JavaTest Harness harness Test Manager window, the agent
  GUI, and the following list of actions  as a guide when troubleshooting
  problems running passive agents:
- 
Verify that the agent was started before the JavaTest Harness harness started the test run. If not, repeat the test run.
- 
Verify that the port value used when starting the agent matches the port value used by the JavaTest Harness harness to send requests. 
- 
Check the physical connection between the JavaTest Harness harness platform and the test platform.
- 
Use the Configuration Editor in the Test Manager window to verify that the harness
  is configured to use agents when running tests. See the JavaTest Harness
  User's Guide: Graphical User Interface for detailed description of the
  Configuration Editor and the Test Manager window.
- 
If you are running the tests using multiple Java Virtual Machines, use the Configuration
  Editor window to verify that the path you provided in the Java Launcher question
  is the path of the  launcher for the agent running tests.
-  If tests are failing or have errors, check the error messages displayed
  in the Test Manager window. If the error indicates that tests are failing because
  of missing classes, perform the following actions:
  
    -  Verify that the class paths used to start the agent are correct. 
-  Use the Configuration Editor window to verify that the harness is correctly
      configured to use the agent on the test system. 
-  Run the agent using the -traceoption to verify that the
      paths in the stream messages for the test are correct. If the paths are
      not correct for the test system, creae a map file for
      the agent to use in translating host-specific values into values that the
      agent can use. See Creating a Map File
-  If a map file was used to run the test, use the Test Run Messages pane
      to verify that the -mapArgscommand is present in the stream
      messages. If the-mapArgscommand is not present, verify
      that both the agent and the harness are configured to use the
      map file. Use the Configuration Editor window to verify that the harness
      is configured to use the agent map file.
 
Copyright © 2001, 2011, Oracle and/or its affiliates. All rights reserved.