ObjectDB Database Search
1-50 of 102 resultsLogging archive contains non-objectdb log files Hi, I'm dealing with problem, that objectdb's log archive folder contains several other log files which are not part of objectdb. We use single location for our application log files and also objectdb log files. When application crashes or retarts, we noticed that several of our log files reside | |
Can I Disable the Creation of the "log" Directory? (attached to forum thread mentioned above), I disable logging (by setting log path="") but the " log " directory still gets created. A " log " directory also gets created when I run com.objectdb.Enhancer ... to ignore these " log " directories, which is a minor annoyance. Can the creation of " log " directories | |
Failed to write to ObjectDB log file\ log \odb20130502. log my program is a Cytoscape plugin. marcins Marcin ObjectDB has no permission to create a log file at the default path. Possible solutions: Change the location of the log files to another path . Grant the ObjectDB process permission to write to that path. Disable logging by | |
Is redirecting the log file possible). This directory is protected by the O/S and therefore objectdb has problem creating its log file. Relaxing ... the EntityManagerFactory (or is it the EntityManager?) where to store the log -file somewhere more convenient? Knut Hansson Knut Hansson Yes, you can configure the log path . support Support That did it - many thanks! Knut Hansson Knut Hansson | |
Failed to create a new file 'target\objectdb\log\archive' (error 112) "target\objectdb". The folder "target\objectdb\ log " does not exist yet. Do we have to create ... .server:integration-test] Failed to create a new file 'target\objectdb\ log \archive' (error 112) [11 ... , which should create the log directory if it does not exist yet (and there are sufficient privileges). support Support | |
ClassNotFoundException messages in the log file In the ObjectDB log file, I still see one ClassNotFoundException. Is this to be expected, or ... .BackgroundThread.run(BackgroundThread.java:148) CBE CBE This stack trace is normal when logging is enabled at DEBUG level. You can reduce the logging level of "type.loader" to WARNING to avoid | |
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 ... logging globally. But you can decrease logging level for this specific subject, by updating | |
log entry date/time It would be very useful if each entry in the log file has a date/time stamp. Thanks, Carl FastModel Ben Schreiber Version 2.2.2 adds date/time stamps to the log . Thank you for your suggestion. support Support | |
JPA Entity Fields and logging , even if the application doesn't use them directly. Version values can't be preserved | |
Index Definition . The optional name attribute has no specific function but might appear in the ObjectDB Explorer and in log | |
Deleting archive log folder causes exception Hello, we have observed strange behaviour when we delete odb archive log directory. We are running long term tests and during it we are deleting all logs that are not needed keeping the system running. When the "archive/" folder, where odb logs are archived, is deleted, the exceptions occur: [2014 | |
General Performance Issues Illustrated with a Specific Method the Explorer schema tab). You should also run this query with logging enabled in the configuration ... for that. Below is the relevant log . [2023-09-23 00:13:10 #168 query.manager] Query "select ... ; MOH-SL Ministry of Health Sri Lanka The log XML | |
Getting com.objectdb.o.UserException:\Tomcat 4.0\webapps\Expresso\WEB-INF\ log \odb20120904. log ' at com.objectdb.o.MSG.d(MSG.java:74 ... .FileNotFoundException: file:C:\Program Files (x86)\Apache Group\Tomcat 4.0\webapps\Expresso\WEB-INF\ log \odb20120904. log (The filename, directory name, or volume label syntax is incorrect) at java.io.RandomAccessFile | |
after upgrade to 2.9.0 database destroys, urgent issue at our most important customer, production shutdown/becomes unusable, see doctor report and current log , urgent help required, production of a 500 ... we are currently uploading the database that was repaierd and the logs , as soon as available we send a link. We did not do any schema changes hgzpincher Hans-Georg Zwicker Looking again in the log | |
jakarta.persistence.PersistenceConfiguration.PersistenceConfiguration(String) the persistence provider for logging and error reporting Since: Jakarta Persistence (JPA) 1.0 | |
Trouble viewing db in Explorer..odb Brian Please check the log file. It should include a more detailed exception stack trace. support Support The log file systematically list all class in the following manner: [2012-06-11 11:31:51 ... it is not related to the reported problem (it is written to the log file only when the logging level | |
Failed to commit transaction: Attempt to commit a rollback only transaction the database file with the ObjectDB Doctor and look for exceptions in the log file. support Support ... the server log could help. support Support ok, so, firstly: the problem is definitely related ... to the last ObjectDB build for both the client and the server. Enable debug level logging | |
Mismatch client-server protocol prefix with this exception. Please check the log files for other exceptions, possibly before this exception is thrown ... . They should go away after upgrading to the newest underscore release I suppose. I also checked the logs ... much control what happens to the entity manager. From what I see from the logs Spring reuses | |
virtual servers and one file; objectdb.conf file that is not is use). Check which configuration file in actually used in the log ... logging with the level info. It is noticeable that again and again the message "Large number ... ." appears. I have attached a RAR archive with more logs . I hope this helps to identify the problem | |
newbie - lots of exeptions to glass fish and invoke methods there (fine with postgresql) . here is our log ... with the new build and see if new exceptions are logged . support Support Hi Again, We now have the an issue with log details below ... We're trying 6 again to make sure we haven't broke again SEVERE | |
Post-compile enhancement fails when static Log4j 2.5 based logger used in Entity a non-static logging variable holder can be used in an @Entity. ObjectDB 2.6.3 ... extends Element { On post-compile enhancement I get this error (as reported in the odb log file ... .apache. logging .log4j.core.config.xml.XmlConfiguration.(XmlConfiguration.java:97) In the build.xml Ant | |
EntityManager creation taking long time during the time of issue: From our logs the issue seems to have occurred between 3:45 am to 4:15 am on Nov 22nd ... , are the client and server on the same machine/VM? Do you see anything relevant in the ObjectDB log files (check both client and server log files if client-server is used). If you try | |
Possible cause for "Enhancement of type ... is old and cannot be used" We get the following log : [2015-06-08 13:07:02 #1 type.user] Enhancement of type com.btc.ep ... issue that is not related to this forum thread. Your log in that report also included "Enhancement ... common logging services); nearly every other domain entity in the system inherits from Element | |
Deadlock in objectdb code, so they aren't first encountered later? Also, is there a logging option to follow schema ... can find managed classes automatically . Also, is there a logging option to follow schema changes ... . support Support Thank you for your fast and effective response to my issue - the new logging option should help solve things. sjzlondon Steve Zara | |
StackOverflowError after commit? If you can provide a full stack trace (possibly from the log file) it could help. support Support we use ... the full stack trace in the ObjectDB (client side) log file. support Support we have solved this issue ... log had following stacktrace, it is possible to throw a better exception? com.objectdb.o | |
Failed to read DB file while online backup is running The new stack traces 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 : Stacktrace 1: [2015-06-11 13:12:41 #4 *] java.lang.NullPointerException at com.objectdb.o | |
Jboss 6 persistence.xml startup error.conf , the ObjectDB log directory is deploy/ log , and the database is created by default at deploy/db | |
Filename.odb$ Persisting Issue. using a debugger or printing to log o console). It will not be reached and executed if the application ... the ObjectDB log file to see if every database opening is followed by closing it. support Support | |
Online backup problem Hi, We are trying to create a servlet that performs database online backup. Unfortunately, even though no exception is thrown, backup files aren't created. When I turn on DEBUG logging in ODB, I ... ;that is shown only in logging at DEBUG level is normal (part of the class searching process | |
How to Use a SF with extended Persistence Context? [org.jboss.as. logging ] JBAS011502: Removing bootstrap log handlers 13:52:02,001 INFO  | |
OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011).moxydox.server.BackgroundThread.run(BackgroundThread.java:148) CBE CBE The log file ... log includes "Building a synthetic Class" messages, such as: [2017-11-03 09:40:29 #5 type.loader | |
Database corrupted after schema change BDOWA.attributes is also missing in the list. Neither ObjectDB log , nor the application log wrote any errors, so it looks to me that it is some failing schema evolution. When I tried | |
Connection is closed Caused by: java.io.EOFException so much on my own logs that I neglected the ObjectDB logs ! The cause is more obvious from | |
Replication failed Dear support members, I am trying to set up a replication url in objectdb.conf and have the the following error in the log files: [ObjectDB 2.3.4] javax.persistence.PersistenceException Failed ... Clemens Kunwald It is unclear why you get this exception. Check for additional stack traces in the log | |
Catching exceptions from online backup it. There is some handling of the exception like writing it into the log file with trace level ... ( InterruptedException e ) { LOG . error ( e ) ;   | |
Unable to convert 1.x odb file to 2.x broken references More information can be found in the log Relevant part from the log file: [2014-05-06 | |
disabling JDO in objectdb embedded mode/metamodel-ear-1.0-SNAPSHOT/lib/commons- logging -1.2.jar, URLEntry : file:/usr/local/glassfish/glassfish ... . The trace in #1 is the best I can show to explain the problem. (I can also add a log file if you like | |
retrieval again and again started but probably worth trying) + improved log , which expects to add additional stack traces to the log in ... Support we do have the retrieval again, see attached log . The queries mentioned here are completely ... in this log seem different than in the original post, so hopefully build 2.9.0_02 did solve the main | |
combined index not used to the log if this threshold is exceeded again. Ability to manually select the query plan ... plans and selecting the best manually: The log panel shows the position (in the list of query plans ... Zwicker You can see all the query plans in the log if you enable logging for queries in trace level | |
Negative snapshot user count exception I found the following stack trace in my log files; it's cropped up a number of times: [2013-08-23 ... (see attached 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]), this error | |
Server crash - Mismatch client-server protocol prefix;I've reviewed the server-side logs , and there are no events logged shortly before the crash.   ... between the two issues is that I discovered issue #206 while examining the logs , hunting for a clue ... ). Other issues I noted in the log were some out-of-memory errors (although I'm running with -Xmx1024m | |
Unexpected exception (Error 990) com.objectdb.o.InternalException.Worker.run(Worker.java:54) The Log file: (It contains two error ... .eclipse.core.internal.jobs.Worker.run(Worker.java:54) In this case, the log file was not created ... :45) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Log file: [2015-03-06 18:15:01 #1 | |
[ObjectDB 2.2.6_02] Unexpected exception (Error 990) at com.objectdb.o.OBC.aJ(OBC.java:961).BigInteger; import java.util.Calendar; import java.util.GregorianCalendar; import java.util. logging .Level; import java.util. logging .Logger; import javax.persistence.EntityExistsException; import javax ... .getName()). log (Level.SEVERE, null, ex); } } private EntityManagerFactory emf; public ReproduceTest | |
Unexpected exception (Error 990) - NullPointerException 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 | |
ArrayIndexOutOfBoundsException on flush which blew out the logs : Attempt to commit a transaction after failure in writing to database file 'F ... transactions could help if replaying them reproduce the problem and you can share these logs . Large objects | |
ClassCastException thrown when running count query for the fields in the query. Log of the query execution using DEBUG logging level. support Support Hello | |
query returns failed to read from database file we have since today exceptions on executing some queries like this: Failed to read from file 'F:\Hummingbird\Objectdb\db\coreSystemDb.odb' we are using objectdb 2.7.2_05 in the objectdb log ... ) hgzwicker Hans-Georg Zwicker Please post the full stack trace from the ObjectDB log file. support Support | |
Close() Method of EMF throwing "PersistenceException: Connection is closed" on first attempt to close. the context in which this problem occurred, please check the ObjectDB log files on the server ... and just writing the condition to a log file, because if the database connection is closed, further attempts to close it are not necessary. support Support | |
ArrayIndexOutOfBoundException get the exact scenario to simulate. There is log from ObjectDB: java.lang.ArrayIndexOutOfBoundsException ... .ArrayIndexOutOfBoundsException We found similar problems in more logs : java.lang | |
ObjectDB 2.9.1 Added support of embedded path expressions to mappedBy fields ( issue #2917 ) Fixed the SectionClassifier retrieval bug ( issue #2912 ). Fixed log file location for some server log messages ( issue #2914 ). |