Internal Website Search
111-120 of 200 resultsRefreshConfiguration Advice;log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info" /> < | |
Setting temp directory location in ObjectDB" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info" /> < | |
locks on pure query activities;url-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" /> | |
Performance tuning, best practices="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> | |
Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found Hello! ObjectDB logs these errors when I start the app and open the log in page ... ObjectDB's logs and I was wondering why. zmirc Mircea Chirac The exception is thrown ... decrease the logging level of this ObjectDB component to ERROR: | |
NullPointerException while setting a new property value me? Thank you. Cabot Vitas Lada Please check your ObjectDB log file ... > Here is the log file in DEBUG mode, but there is nothing special or detailed error description. https://dl.dropbox.com/u/51625311/objectdb.log (attaching files | |
How to disable use of graphic windows by objectDB the log file for additional errors / exception stack trace. support Support I've checked the log file, but has the same message. [root@GhostRider bin]# cat ../log/odb20111024.log | |
Performance Issues After Migrating to ObjectDB - Urgent Assistance Required" password="true" /> <log path="$objectdb/log/" max="64mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> | |
Query results are not up to date for entities, not primitives="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> | |
Error on commit seems to be healthy. These stack traces are normal when using DEBUG level logging. As the result of the exception in #1 you should have in the log file lines such as: support Support I re-ran to get a clean log file and the doctor must have fixed it. (possible |