Troubleshooting Service Runtime Errors

Problem: Service runtime errors.

Problem 1: When a deployed package contains two or more services that are configured to use a file transport as the inbound transport, Sybase WorkSpace live locks and the CPU system usage increases to and stays at 100%.

Solution 1: A service defined with a File inbound transport locks the designated file directory after deployment. Live lock occurs if a second service also attempts to consume inbound messages from the same file directory. Therefore, you must verify that the inbound file transport defined for each service is a different file transport. Only single thread access is supported for inbound file transports. If two or more services are publicly accessible with file transport, each must be defined to use a separate file directory.

Problem 2: By the time the service is successfully deployed into the application server and is ready to run, the service is syntactically correct and complete. Errors that occur at the execution stage are due to semantic errors such as logic errors.

Solution 2: Test the service in the Sybase WorkSpace tooling:

  1. Open the Enterprise Explorer.
  2. Expand the package folder under Service Containers to display all the services contained in that package.
  3. Right-click a service name, and select Test Service.
  4. Use any of these test modes:

    • Dialog Service Test Wizard

    • SOAP Request/Response Service Test Wizard

    • Create Web Service Client Wizard

  5. Review the SOAP response message that appears in the Response Message area of the Service Testing Wizard dialog window.
  6. Capture the request and response in the SOAP Inspector:
    1. Open the SOAP Inspector view.
    2. Start the SOAP Inspector. Click On.
    3. Select Enable proxy settings on the Options page of the Service Testing Wizard.

      Setting a proxy setting means that the soap request of a service invocation will be redirected to the host and port specified and captured by the SOAP Inspector before the request or response is forwarded to the target.

  7. Review this log file: installation directory\DevRuntimes\EAServer\logs\MyHostName.log
Parent topic: Troubleshoot

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.