Internal Website Search

If I turn the log level in objectdb.conf to debug I get a lot of It is the normal behavior when using debug level logging globally. But you can decrease logging level for this specific subject, by updating the configuration:

It would be very useful if each entry in the log file has a date/time stamp. Thanks, Carl   FastModel Ben Schreiber Version 2.2.2 adds date/time stamps to the log. Thank you for your suggestion. support Support

It seems that there is a bug in logging mechanism, if you try to start the database which is already started it starts filing the log continuously until it runs out of space on disk. How to check is the database runing from command promt. regards.

Hi we have found that when restarting the database in contrast to making stop/start database log doesnt contain any data. Does anyone have similar issues. logging messages, e.g. [2014-02-07 13:00:00 #1 server] Server

I'm trying to track down an issue in an application - the problem occurs around the retrieval of an object from a database the specifics are unclear at the moment. In the objectdb log the following message is written everytime the issue occurs

We have since a while these entries in the log, please inform if this needs a repair (doctor):   log (e.g. moving

we have the following entries in our objectdb log (system continues to work normally, database was repaired before switching to version 2.7.5):   [2018-05-14 15 ... > hgzwicker Hans-Georg Zwicker This log entry indicates an unexpected condition during retrieval

we have in the log entries like:   [2020-06-03 16:13:06 #17 store]  RetrievalTask.reportPrimaryResult0: page#48835201, reader.getPos() = 323 [2020-06-03 16:21:37 #18 store]  RetrievalTask.reportPrimaryResult0: page#16686765, reader

clicky_log_download">JPA Web App - Maven Project (6KB) If 

clicky_log_download">Spring MVC JPA - Maven Project (8KB)