About log

51-60 of 200Refresh
Forum
2

First query takes 4+ minutes to complete

-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" /> logs? 2
Forum
2

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 ... . Since there are no messages in the master log, maybe this is not exactly a maser failure but a failure to access
Forum
2

ODB IndexActivation NullPointerException

e) {         log.debug("Thread interruped during join the 'ODB-IndexActivation' thread ... {         indexActivationThread.join();     } catch (InterruptedException e) {         log.debug("Thread interruped during join the 'ODB-IndexActivation' thread");     } } else {     log.debug("Thread ODB IndexActivation
Forum
2

Replication Issue

" user="true" password="true" />                 <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" />                 <log-archive path="$objectdb/log/archive/" retain="90 ... database manually to the salve side (under the $replication directory). Please also check if the log files include additional stack traces. EKK
Issue
2

Server crash - Mismatch client-server protocol prefix

reviewed the server-side logs, and there are no events logged shortly before the crash ... the two issues is that I discovered issue #206 while examining the logs, hunting for a clue regarding ... AM, 8/30 @ 7:41 PM, 9/1 @ 12:15 PM (all times PDT). Other issues I noted in the log were some
Issue
1

Blocked by find

(if this is the problem) may require few iterations of trying special ObjectDB builds that will log ... will be logged. See attached for a test which I think replicates the problem. It is a simple persist ... logging though - I've checked that it is definitely set by doing a System.getProperty just before
Forum
1

Degrading performance overtime

-timeout="0" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain
Forum
1

EntityManager.refresh takes a long time

EntityManager.refresh takes a long time for entity object Person in this code:     logger.log ... > persons = personQuery.getResultList();                logger.log(Level.INFO, "end select for person " + new Date().toString());                for(Person person : persons) {         logger.log(Level
Issue
1

Error on commit

seems to be healthy. These stack traces are normal when using DEBUG level logging. As the result of the exception in #1 you should have in the log file lines such as: BTree ID: BTree Name: BTree Page: Request code: ... Please post them. I re-ran to get a clean log file and the doctor must have fixed
Forum
1

Exception when dataset bigger than treshold

" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" />