Troubleshooting Java Service Runtime Errors

Problem: Runtime errors in a Java service.

Solution: Use the following sequence to troubleshoot Java service errors during runtime.

Note:

To avoid complications towards the end of your developoment phase, you should test your existing Java classes before you include them into a Java composite or business process service.

  1. Check for errors in the installation directory\EAServer\logs\MyHostName.log file.

    As an alternative to adding tracing code, you can step through the service code with remote debugging .

    Runtime errors can occur due to deployment problems or exceptions thrown but not caught in the service code. You can also add your own code to trace service execution. EAServer records any output written to System.out in the log file.

  2. If a composite Java service consumes other services, debug and test each service separately. See the troubleshooting guidelines for each service type you want to debug in the online help. A composite Java service calls other services through generated proxy code. Therefore, any additional supporting classes may also be generated depending upon the complexity of the composite service. You can add tracing to generated classes with the System.out.printIn statements or step through this code with remote debugging.
Parent topic: Services
Related tasks
Troubleshooting Service Runtime Errors

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.