8 | Master database switching to read-only mode, possibly caused by slave failure and there was nothing in the server DB logs. All write requests sent to master after this time have failed with the same exception. 13:25:59 - the slave closed it's database - the following was in the logs ... such situation. Since there are no messages in the master log, maybe this is not exactly a maser failure |
7 | Trouble viewing db in Explorer. the log file. It should include a more detailed exception stack trace. support Support The log file ... related to the reported problem (it is written to the log file only when the logging level is DEBUG |
7 | 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 |
7 | 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 |
7 | Mismatch client-server protocol prefix next requests to fail with this exception. Please check the log files for other exceptions, possibly ... after upgrading to the newest underscore release I suppose. I also checked the logs of our other apps ... to the entity manager. From what I see from the logs Spring reuses them and creates new ones |
7 | 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 |
7 | Query results are not up to date for entities, not primitives="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info" /> </general> <database |
7 | OutofMemory error with Object DB 2.0" password="true" /> <log path="c:/temp/odb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="c:/temp/odb/log/archive/" retain="90" /> <logger name="*" level="fatal |
1 | Enhancing a class causes it to not save changes., everything works perfectly. In reflection mode, the objectdb log on debug mode refers to classes ... logs for both the enhanced and unenhanced versions, and the objectdb.conf. -------------Update ... .log. As far as I can tell, it's not causing any problems, so feel free to tell me to take a hike |
1 | Internal error of throwing the exception will write information to the log and proceed (ignoring that unexpected state ... can give you feedback soon. sjzlondon Steve Zara Please try build 2.7.2_07 and report new log messages ... . Will report back log entries soon. sjzlondon Steve Zara I believe I may have found a possible cause |
