Internal Website Search

must match one of the query plans logging text. Logging format and text might have changed between ... nothing now. To check the up to date logging text of query plans that used that index run the query with debug logging: <general>  ... <logger name

;   o commons-logging:commons-logging:1.1.1         ... .TimeBasedRollingPolicy - Will use the pattern time_example-%d{yyyy-MM-dd}.log for the active filelog'. 09:30:08,884

;          <log path="$objectdb/log/" max="8mb ... ;     <log-archive path="$objectdb/log/archive/" retain="90" />    ... ;        <log path="$objectdb/log/" max="8mb" stdout="true

-history size="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> ... ;   <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" />   <

> Database size is only 67MB, heap size is set to 1536MB. Log files are empty. Database uptime was about 3 ... of record log file. For now I turned on heap size monitoring and I will try add more details ... > Record log is almost 50MB large. Database is about 73MB large. The strange thing

because ObjectDB doesn't have a permission to create a log file in the default path (as specified in ... ). See the manual for explanation on the log directory ... log path, or change ObjectDB home, or change the log path by adding your own configuration file.

(InstantiationException ex) { logger.log(Level.SEVERE, null, ex); } catch (IllegalAccessException ex) { logger.log(Level.SEVERE, null, ex); } catch (IllegalArgumentException ex) { logger.log(Level.SEVERE, null, ex); } catch

, which fixes the "composite index not used" and a new warning to the log if this threshold ... >The log panel shows the position (in the list of query plans) of the executed query plan (always 1 ... of query plans ? hgzwicker Hans-Georg Zwicker You can see all the query plans in the log

, we encountered an issue with the logging mechanism. We enabled full logging (logger name="*" level="debug") and logged to a file with limited size. We did not configure a log-archive (log-archive path="" retain="0"). That caused an exception when the log file reached its size limit. Here's the stack trace

an idea - what I would find helpful is some form of logging of the making persistent of objects, I ... ; } } } } Do you have any idea how to change this test case to reproduce the exception? Debug logging ... log lines? Thanks. support Support Sorry for the delay - it takes time