|
#39808
|
Exceptions and/or constraint violation received when shutting down members or executing concurrent DDL
|
When SQLFire members are frequently shut down down or DDL statements are being executed concurrently, SQLFire may throw a "conglomerate does not exist" exception or a LockTimeoutException. The client driver may throw a ClassCastException or a false constraint violation.
|
Retry the operation that received the exception.
|
|
#44245
|
Server restart fails with "java.lang.ClassCastException: [[B cannot be cast to [B"
|
In some rare scenarios when more than one servers are restarted concurrently then startup of a server may fail with "java.lang.ClassCastException: [[B cannot be cast to [B".
|
Restart the server when no other concurrent server starts are being done.
|
|
#44246
|
Memory overhead may not decrease for a table with overflow if there are local indexes on the table
|
Currently local indexes in SQLFire are always in memory and try to reuse the in memory data of the table itself directly to avoid additional overhead. However, in some cases the index hangs on to table data for a table configured to use overflow as eviction even after it has overflowed to disk. This can cause memory overhead to not reduce for a table even after overflow to disk is happening properly after hitting the eviction limit.
|
|
|
#44249
|
Product may sometimes throw SQLException with state XSDA4 in out of memory situations rather than XCLS4 used in most cases.
|
In some cases a generic SQLException with state XSDA4 may be thrown instead of the more specific XCLS4 for queries/DMLs/DDLs canceled due to out of memory situations. In such cases the exception stack shows "com.gemstone.gemfire.cache.LowMemoryException" as the root cause.
|
Application needs to handle both XSDA4 with LowMemoryException as the cause, and XCLS4 to interpret as query/DML/DDL cancellation.
|
|
#44257
|
Excess logging when statement-level statistics are enabled
|
When enable-stats is set to true on a connection, or globally using the sqlfire.enable-stats system property, logging at info level appears in the fabric server system log files each time a statement-level statistic is incremented.
|
Run with logging at config level.
|
|
#44289
|
DdlUtils example build.xml file hangs in the ImportDataToDB target
|
When you use the example DdlUtils build.xml that is installed with SQLFire, DdlUtils hangs in the ImportDataToDB target. This occurs because of a defect with batch mode handling in the JDBC thin client driver when autocommit is enabled. The example build.xml file enables batch mode by default, by setting the "usebatchmode" attribute to "true" in the writedatatodatabase task.
|
Disable batch mode execution in the build.xml file by changing the "usebatchmode" attribute to "false" in the writedatatodatabase task (usebatchmode="false").
|