7 | 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 |
7 | The server cannot start in CentOS" threshold="64mb" /> <network inactivity-timeout="0" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger |
7 | IN expression in a Criteria Query (you should be able to see it in the log, if you enable logging as explained in this forum thread, or by converting ... from logs: <token name="QUERY" code="67" postion="0:0"> <token name="SELECT" code="132" postion ... I have just tryed 2.5.0_02, but the problem with criteria query is still there. Log shows |
7 | newbie - lots of exeptions fish and invoke methods there (fine with postgresql) . here is our log ... with the new build and see if new exceptions are logged. support Support Hi Again, We now have the an issue with log details below ... We're trying 6 again to make sure we haven't broke |
7 | Post-compile enhancement fails when static Log4j 2.5 based logger used in Entity a non-static logging variable holder can be used in an @Entity. ObjectDB 2.6.3_04 Apache Log4j2 - 2.5 ... { On post-compile enhancement I get this error (as reported in the odb log file): [ObjectDB 2.6.3_04 ... .logging.log4j.core.config.xml.XmlConfiguration.(XmlConfiguration.java:97) In the build.xml Ant script |
7 | Failed to commit transaction: Attempt to commit a rollback only transaction the database file with the ObjectDB Doctor and look for exceptions in the log file. support Support yep ... is the solution. support Support In addition - the complete stack trace from the server log could help. support ... to the last ObjectDB build for both the client and the server. Enable debug level logging |
7 | Degrading performance overtime-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/" retain |
7 | 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 |
1 | Threaded Test - Failed to commit transaction: Unexpected internal exception) it seems to just hang on the "take" commit. I've attached the objectdb log from these runs if that helps ... from my log and the objectdb log. felixobjectdb Richard Szurgot This was another bug. Please try ... the javaagent method but to no avail. I've put some timing around the logging to show the slowdown better |
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 |
