Internal Website Search

a full stack trace (possibly from the log file) it could help. support Support we use version ... stack trace. Please find the full stack trace in the ObjectDB (client side) log file. support ... instead of @Entity the objectdb error log had following stacktrace, it is possible

seem partial. Could you please check for more details in the log? support Support You are right I just found the full stack traces in the odb log file rather than the normal application log

fast. zmirc Mircea Chirac Update: today it works pretty fast, but I can't log in using Chrome and Firefox (discussed in other thread). The log in seems to work, after I enter my credentials, but the website still shows me as not being logged in, so something is wrong. zmirc Mircea Chirac

-history size="0" user="false" password="false" /> --> <!-- error if missing <log path="" max="8mb" stdout="false" stderr="false" /> --> <!-- error if missing <log-archive path="$objectdb/log/archive/" retain="90" /> --> <!-- ok if missing <logger name

.Calendar; import java.util.GregorianCalendar; import java.util.logging.Level; import java.util.logging.Logger; import javax.persistence.EntityExistsException; import javax.persistence ... ); } catch (Exception ex) { Logger.getLogger(ReproduceTest.class.getName()).log(Level.SEVERE

exception. In fact an error on the given position doesn't show up on the log of the client code. I just found out about the null pointer by writing an interceptor annotation that logs all exceptions. Without this interceptor the log file only stated, that the transaction has been marked

After an unexpected server shutdown and restart of our application we have these messages in the log (complete log attached): … [2018-03-26 14:39:30 #1096 store ... Zwicker The log indeed shows that the database was recovered from an unexpected shutdown

> - Put important log info to the console as well - Provide possibility to not only create new ... /stop/restart messages are printed to the standard output, but you can direct all log messages to the standard output and/or the standard error by log_element

ObjectDb on our production server.  These are being written to a log by a server wrapper which runs ... them to bubble up into the wrapper, which writes them to it's log file.  The stack traces ... up in the ODB log, and why they are bubbling up out of ObjectDb's code to the service wrapper?

workspaces and tried to create a new report.  This created an error in the Error Log.  I've captured the error log output here.  I confirmed that the directory C:\Users\kwhittin\new ... > is empty... Log dump: eclipse.buildId=4.5.2.M20160212-1500 java.version