Internal Website Search

; <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info" /> < ... so much on my own logs that I neglected the ObjectDB logs!   The cause is more obvious from

you for this clarification. Some more information may help. Are these exceptions written to the log ... side effects except getting these exception in the log. You wrote: > ... written to the log? thrown? stop anything? In this particular case

>ODB Log prints nothing: [2021-04-16 18:26:25 #1 server] Server on port 10054 ... ]) = 0 Here is example of strace log during standard connection made from our app: [pid 26632] 12:04 ... for observations. So no connections. The heap dump was taken from scripts, which is reading strace log as I

down if the port communication is idle, or some similar inactivity. When inspecting the log it doesn’t show anything why the database has stopped. DB can be normally started after it shutdowns and log continues. Logging is currently set to TRACE level. ObjectDB is running on CentOS, and it doesn’t show any

used in the log. You may also insert a deliberate  .result {padding : 2px 4px 0 4px;} .top-row

.conf and have the the following error in the log files: [ObjectDB ... " threshold="64mb" /> <network inactivity-timeout="0" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain

again we have at another customer after weeks of no problems these entries in the log ... >When these "RetrievalTask.reportPrimaryResult0' are written to the log, exceptions with more details are also thrown. Have you seen such an exception in the log file (on the server or the client) or thrown

I found the following stack trace in my log files; it's cropped up a number of times ... log file). Last week I had inadvertently left the database running with inadequate ... ; After restarting the database (see log entry [2013-09-10 02:44:10 #1 server

" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger ... in your log files (or in ObjectDB log files if you enable logging queries). If repeating

it could help. If you can repeat the error we can release a new build that will log relevant information to the log when this exception is thrown, for further diagnosis. support Support Hello ... that will log relevant information to the log when this exception is thrown, for further diagnosis