Home » Search

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

Failed to commit transaction: Attempt to commit a rollback only transaction

for exceptions in the log file. yep, so creating a new database removes this problem. ie: somehow the database ... is the solution. In addition - the complete stack trace from the server log could help. ok ... build for both the client and the server. Enable debug level logging for both the client and the server
Forum
2

How to disable use of graphic windows by objectDB

known     Please check the log file for additional errors / exception stack trace. I've checked the log file, but has the same message.   [root@GhostRider bin]# cat ../log/odb20111024.log
Issue
2

Internal error

. We can release a new build that instead of throwing the exception will write information to the log ... , so I can give you feedback soon.   Please try build 2.7.2_07 and report new log messages ... back log entries soon. I believe I may have found a possible cause of the internal error:  I