6 | ClassNotFoundException messages in the log file when logging is enabled at DEBUG level. You can reduce the logging level of "type.loader" to WARNING |
6 | Log4j error this error somehow changes our logging level to DEBUG. Is there possibility that ObjectDB's logging |
6 | ClassCastException on SELECT NEW ... after UPDATE over Java RMI does not fix the problem. We need guidance on how to debug and fix the problem. Thank you Emil |
6 | OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011) have attached two ObjectDB logfiles ("debug" level). The "Works_xxx" file is from the build computer |
6 | evictAll() behavior). support Support hi I've checked in debuger that every data model class has fileds like |
6 | Log is almost empty (log level 'trace')Hi, Using 2.4.6_01 version on Linux (2.6.18, VPS).. Just wondering what should I suppose to see in a log file with a log level 'trace'/'debug'.. Trying to fix an issue that server version sometimes accidentally quits without any notice.. My log file (independently on whats specified in config file |
1 | ClassCastException thrown when running count query for the fields in the query. Log of the query execution using DEBUG logging level. support Support |
1 | objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active' class diagram of @Startup collaboration in latest test web app: The full debug logging |
1 | NullPointerException using with "refresh" method can use an older version to avoid this problem. There is no time for debugging. itsme Martin Petzold |
1 | NoResultException: No matching results for a unique query on!?? Here's the stacktrace (copy+paste from debug output): com.objectdb.o.MSG.d(MSG.java:61) com.objectdb.o.PRG.af(PRG |
