Problem: Runtime errors in a Java service.
Existing Java classes should be tested before inclusion into a Java composite or business process service to alleviate complications at a later stage in development.
Solution: Use the following sequence to troubleshoot Java service errors during runtime.
Check for errors in the <installation directory>\Sybase\WorkSpace\DevRuntimes\EAServer\bin\Jaguar.log file.
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 the System.out in the log file.
As an alternative to adding tracing code, you can step through the service code with remote debugging.
If a composite Java service consumes other services, debug and test each service separately.
See the troubleshooting guidelines for each service type in the online bookshelf.
A composite Java service calls other services through generated proxy code; thus, 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.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com