8 | config optimizing" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info |
8 | type.loader java.lang.ClassNotFoundException) Glassfish3.0.1 With server logging turned on I get the following error message for many (or all) encountered ... With logging enabled in debug level - some 'normal' ClassNotFoundException are written to the log - so please check if you still see these exceptions in lower logging level (e.g. info). The empty |
8 | Setting temp directory location in ObjectDB inactivity-timeout="0" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info |
8 | 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" /> <logger |
8 | Performance tuning, best practices" /> <network inactivity-timeout="0" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive |
8 | Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not foundHello! ObjectDB logs these errors when I start the app and open the log in page. (see attachment ... of User entities works also. This just appears in ObjectDB's logs and I was wondering why. zmirc Mircea ... this exception, or decrease the logging level of this ObjectDB component to ERROR: <logger name="enhancer |
8 | NullPointerException while setting a new property value Vitas Lada Please check your ObjectDB log file (mainly on the client side, but server side as ... error. 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 seems to be broken too...) java |
8 | How to disable use of graphic windows by objectDB not known LottaLava Edson Alves Pereira Please check 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 |
8 | Performance Issues After Migrating to ObjectDB - Urgent Assistance Required" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log/" max="64mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log |
1 | Error on commit DEBUG level logging. As the result of the exception in #1 you should have in the log file lines ... re-ran to get a clean log file and the doctor must have fixed it. (possible index issue?) This is from the original odbYYYYMMDD.log file: (*** = Employer public forum policy) [2012-04-20 11:56:07 #200 |
