Using Trace Flags for Advanced Debugging

SQLFire provides debug trace flags to record additional information about SQLFire features in the log file.

SQLFire provides these trace flags that you can use with the sqlfire.debug.true system property to log additional details about SQLFire behavior:
Trace flag Enables
QueryDistribution Detailed logging for distributed queries and DML statements, including information about message distribution to SQLFire members and scan types that were opened.
StatementMatching Logging for optimizations that are related to unprepared statements.
TraceAuthentication Additional logging for SQLFire authentication.
TraceDBSynchronizer DBSynchronizer and WAN distribution logging.
TraceIndex Detailed index logging.
TraceJars Logging for JAR installation, replace, and remove events.
TraceTran Detailed logging for transaction events and operations, including commit and rollback.
TraceLock_* Locking and unlocking information for all internal locks.
TraceLock_DD Logging for all DataDictionary and table locks that are acquired or released.
If you are asked to set a trace flag for debugging purposes, do so using the sqlfire.debug.true system property when you start a server or locator. For example, this command sets both the QueryDistribution and TraceIndex flags:
sqlf server start -J-Dsqlfire.debug.true=QueryDistribution,TraceIndex
For applications that use the JDBC peer driver, set trace-related flags in the sqlfire.debug.true system property before the application connects to the SQLFire cluster. For example, this code sets traces for index and query distribution and then connects using the peer driver:
Properties props = new Properties();
props.put(“sqlfire.debug.true�?, “TraceIndex,QueryDistribution�?);
Java.sql.Connection conn = java.sql.DriverManager.getConnection(“jdbc:sqlfire:�?);