Using Trace Files to Troubleshoot Streams

<< Click to Display Table of Contents >>

Navigation:  Building Streaming Applications > Troubleshooting Streaming SQL >

Using Trace Files to Troubleshoot Streams

Previous pageReturn to chapter overviewNext page

SQLstream uses the standard Java logging interface (defined in the package java.util.logging) to trace execution for debugging purposes. Trace files can let you troubleshoot stream functioning during development.

Trace files are useful in troubleshooting streams, because they allow you to see when a stream failed and why.

s-Server has two trace logs. The first will be the most useful in troubleshooting streams.

Trace.log This is the "master" trace, which includes all trace information for the entire server.  It is located at /var/log/sqlstream/Trace.propertiesTrace.log

ApplicationTrace.log This contains only trace information relevant to installed application components (such as plugins, user-defined transforms, and SQL statements). It is located at /var/log/sqlstream/Trace.propertiesApplicationTrace.log

Console.log. A timestamped console.log is located in /var/log/sqlstream/console.log

Syslog. The syslog for your system may also provide useful information on s-Server.