About logging

51-60 of 200Refresh
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
Forum
2

ClassNotFoundException messages in the log file

In the ObjectDB log file, I still see one ClassNotFoundException.  Is this to be expected, or do I have another issue I need to correct? [2017-11-03 13:52:01 #18 type.loader] java.lang ... when logging is enabled at DEBUG level. You can reduce the logging level of "type.loader" to WARNING
Forum
2

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 these exceptions? [2013-02-05 10:52:30 #399 ... when using debug level logging globally. But you can decrease logging level for this specific subject
Forum
2

Failed to create a new file 'target\objectdb\log\archive' (error 112)

\objectdb". The folder "target\objectdb\log" does not exist yet. Do we have to create ... to create a new file 'target\objectdb\log\archive' (error 112) [11:47:18]: [com.rbccm.felix ... build, 2.5.1_03, which should create the log directory if it does not exist yet (and there are sufficient privileges). CalculationServices
Issue
2

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
2

Degrading performance overtime

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

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
2

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
2

Exception when dataset bigger than treshold

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