Internal Website Search

21-30 of 200 resultsRefresh

ClassNotFoundException messages in the log file

In the ObjectDB log file, I still see one ClassNotFoundException.  Is this to be expected ... :148) CBE CBE This stack trace is normal when logging is enabled at DEBUG level. You can reduce the logging level of "type.loader" to WARNING to avoid these messages. Add

ClassNotFoundException Stack Traces in the Log File

If I turn the log level in objectdb.conf to debug I get a lot of ClassNotFoundException's (see example below). My question is, is there a way to avoid ... when using debug level logging globally. But you can decrease logging level for this specific

log entry date/time

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

Logging problem on attempt to start a Server that is already running

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.   peric.emil Emil Perić

log problem

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.   regards ... and then starting it, and therefore should produce 2 logging messages, e.g.

SectionClassifier message in log

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

Errors in log to repprt

We have since a while these entries in the log, please inform if this needs a repair (doctor):   log (e.g. moving the database, changing hardware, etc.) it may help in understanding the cause. support Support

merger missing in log

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:00:48 #1 store]   hgzwicker Hans-Georg Zwicker This log entry indicates an unexpected condition

retrieval tas reports in log

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.getPos() = 689 [2020-06-04 23

JPA Web App Tutorial - Maven Project

/515b895a-a6e1-49c0-854c-46a0cd97b674/guestbook-web.zip" class="image download clicky_log_download">JPA