Home
Troubleshooting
While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
Troubleshooting: transports, tests, and resources
Workarounds and solutions for transport diagnostics, creating and running tests, and saving and renaming objects are contained in this topic.
Troubleshooting: WSDL schemas
You can use some workarounds to problems that you might encounter during and after the import of a WSDL schema into HCL OneTest™ API.

Troubleshooting
While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
- Troubleshooting: Installation and configuration
  You can troubleshoot some of the problems that you might encounter when you are installing, configuring, or running HCL OneTest™ API.
- Global problem notifications
  Problems can occur at a time when HCL OneTest™ API cannot display an error message. Instead, a warning icon is displayed. Double-clicking the icon reveals a list of errors.
- Working with HCL OneTest™ API logs
  To configure the HCL OneTest™ API logs, including those for the RunTest command when run from the command line, update the HCL OneTest API logging properties file.
- Working with HCL OneTest™ API Agent logs
  To configure the HCL OneTest™ API Agent logs, including those for the RunTests command when run from the command line, update the HCL OneTest API Agent logging properties file.
- Working with RQMAgent logs
  To configure the RQMAgent logs, update the RQMAgent logging properties file.
- Locating the logging properties files
  When you install HCL OneTest™ API, HCL OneTest API Agent, or HCL® Quality Server including the HTTP/TCP proxy, several logging properties files are added to each installation's home directory.
- Logging references
  You can use the following list of logging-related information to help you find information about the logs that are supported by HCL OneTest™ API. All of the programs use the Java logging framework. For details, see the Java logging framework documentation.
- Debugging failed Windows™ services
  If one of the programs fails to start as a Windows™ service, it can be difficult to determine the cause. Typically the service fails to start but gives no indication of why. The Windows Event log has nothing useful and the process might not have created its log file.
- Troubleshooting: Installation and configuration
  You can troubleshoot some of the problems that you might encounter when you are installing, configuring, or running HCL OneTest™ API.
- Troubleshooting: transports, tests, and resources
  Workarounds and solutions for transport diagnostics, creating and running tests, and saving and renaming objects are contained in this topic.
  - Debugging with the JVM console
    You can use the HCL OneTest™ API JVM console to debug any errors that might occur while you are working with HCL OneTest API.
  - Limitations of topology discovery
    You must be aware of certain limitations in Topology discovery.
  - Limitations of packet capture
    You must be aware of certain limitations of packet capture.
  - WSDL versioning considerations
    Managing WSDL versions is a common problem that is faced by web services developers. Some guidance is provided to help address the problem.
  - Troubleshooting: COBOL copybook schemas
    You can use a workaround to problem that you can encounter after you import a COBOL copybook schema into HCL OneTest™ API.
  - Troubleshooting: WSDL schemas
    You can use some workarounds to problems that you might encounter during and after the import of a WSDL schema into HCL OneTest™ API.
  - Troubleshooting: Messages
    You can use a workaround to a problem that you might encounter when you work with message fields.
  - Troubleshooting: Rational® Quality Manager
    You can use workarounds to common problems that you might encounter when you work with Rational® Quality Manager.
- Troubleshooting: HCL OneTest™ API Agent
  You can use workarounds to common problems that you might encounter when you install and run the HCL OneTest™ API Agent.
- Troubleshooting: HCL® Quality Server
  You can use workarounds to troubleshoot common problems that you might encounter when you use HCL® Quality Server.
- Troubleshooting: HCL OneTest™ Virtualization
  You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.
- Troubleshooting: Software AG webMethods
  You can use workarounds to problems that you might encounter when you use the Software AG webMethods.
- Troubleshooting: Websphere MQ
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® MQ with HCL OneTest™ API.
- Troubleshooting: WebSphere® Application Server
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Application Server products with HCL OneTest™ API.
- Troubleshooting: WebSphere® Portal
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Portal products with HCL OneTest™ API.
- Troubleshooting: TIBCO
  You can use workarounds to common problems that you might encounter when you are testing TIBCO products in HCL OneTest™ API.
- Troubleshooting: Java™ method transport
  You can use workarounds to common problems that you might encounter when you use the Java™ method transport of HCL OneTest™ API.
- Troubleshooting: Java™ applications that use JDBC
  You can use workarounds to problems that you might encounter when you test Java™ applications in HCL OneTest™ API.
- Troubleshooting: HTTP and Web Services
  You can use workarounds to common problems that you might encounter when you use HTTP and Web Services.
- Troubleshooting: TCP UDP sockets
  You can use workarounds to common problems that you might encounter when you use TCP and UDP transports.
- Troubleshooting: Testing on IBM® z/OS®
  You can use workarounds to common problems that you might encounter when you use IBM® z/OS® with HCL OneTest™ API.

Troubleshooting: WSDL schemas

You can use some workarounds to problems that you might encounter during and after the import of a WSDL schema into HCL OneTest™ API.

Table 1. Troubleshooting WSDL schemas
Solutions and workarounds to problems with importing and synchronizing WSDL schemas
Problem	Resolution
Import or synchronizing a WSDL fails with error CRRIT4235E: `error: Type: Warning Error: [CRRIT4235E] Problem occurred during refresh of URL "file:////filename.wsdl", issue was: java.lang.IllegalArgumentException: Illegal character in path at index 49:` The schema might work correctly in other tools or programs.	One or more namespace declarations in the schema contain whitespace characters. The HCL OneTest™ API code libraries cannot work with whitespace characters. To resolve the problem, remove whitespace from namespace declarations: Open the WSDL file in a text editor and search for space characters in any namespace declarations. The index number shown in the error message gives the character count into a particular namespace attribute. Remove the whitespace characters. Reload the schema. Do this task by either deleting the schema from the Schema Library and importing it again, or by selecting the schema and clicking Rebuild Schema.
Loading a WSDL schema fails with a `org.xml.sax.SAXParseException` error. The following message is displayed when loading the file into Schema Library of Architecture School: `[CRRIT4235E] Problem occurred during refresh of URL "file:/ ", issue was:com.ghc.utils.GHException: There was an error parsing your WSDL file :WSDLException: faultCode=PARSER_ERROR: Problem parsing '- WSDL Document -'.: org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.` The following message is displayed on the JVM console when loading the file to the Logical View of Architecture School. No objects are built: `javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing '- WSDL Document -'.: org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.`	White space characters before the XML declaration are not supported by the XML parsing library. Delete the schema from Schema Library or Logical View. Open the WSDL file in a text editor and inspect the first characters on the first line. Remove any whitespace characters. Import the schema again.