ObjectDB Database Search

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

(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

\ 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

password on the Glassfish server and enable "secure admin". Now, log in remotely to the Glassfish ... . Because the "odbxxxxxx. log " file is in use by an java process. If I restart Glassfish, I can delete the folder ... Par Wingfelt Could you please check what happens if you configure ObjectDB to use a log file in

). 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

"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

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

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

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

It seems that there is a bug in logging mechanism, if you try to start the database which is already started it starts filing the log continuously until it runs out of space on disk. How to check is the database runing from command promt. regards.   peric.emil Emil Perić This is caused by

I'm trying to track down an issue in an application - the problem occurs around the retrieval of an object from a database the specifics are unclear at the moment. In the objectdb log the following message is written everytime the issue occurs. Could you give more detail about what this message

I have the following lines in my objectdb.conf file: I don't believe that the $temp property is being evaluated properly here as it creates a new directory "$temp" in the same directory as my execution script. Shouldn't this be logging to the system temp directory? carr.onstott Carr Onstott

and logging , even if the application doesn't use them directly. Version values can't be preserved

. The optional name attribute has no specific function but might appear in the ObjectDB Explorer and in log

we are facing similar problems as we had before, in the log we have a lot of entries merger ... missing + an objectdb exception. Some objects in the system behave strange. This is a part of the log ... ; InternalException ( logs #1225, #3 above) and the corruption of one large ObjectProperty object ( logs #1222 - #1224

= "$objectdb/ log /odb" max = "8mb" stdout = "false" stderr = "false" / path = "$objectdb/ log /odb/archive ... = "true" /                 path = "$objectdb/ log /odb-client ... ;   path = "$objectdb/ log /odb-client/archive/" retain = "90" /          

the log : ... [2019-03-01 11:53:40 #5 store]  RetrievalTask.reportPrimaryResult0: page#27184134 ... This logging information is written in addition to throwing an exception. Do you see that exception in the log ? Maybe it was caught by your application? This log message by itself provides very little

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

) - we have this log entry in our log : ... RetrievalTask.reportPrimaryResult0: page#13887921, reader.getPos() = 1229 ... of such an exception in the log ? Did you get that log error once or is it repeating? Does it happen

We have since a while these entries in the log , please inform if this needs a repair (doctor):   ... information regarding special activity with that database just before the errors started in the log

we have in the log entries like:   [2020-06-03 16:13:06 #17 store]  RetrievalTask.reportPrimaryResult0: page#48835201, reader.getPos() = 323 [2020-06-03 16:21:37 #18 store]  RetrievalTask.reportPrimaryResult0: page#16686765, reader.getPos() = 689 [2020-06-04 23:15:32 #19 store] 

.lang.Object) must be called from elsewhere. The odb logs show: [2016-08-24 16:14:34 #15 type.registry ... interface the runtime error on attempting to persist disappears (but this does not "fix" the log ... operations in interface IValue as shown above. Result:  The odb logs show: [2016-08-24 16:14:34

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

\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

/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

of indexes: When you execute a query in the Explorer in the log pane. In the log file if you enable query logging in objectdb.conf (on the server side): or   support Support Hello, sorry but name ... ? If you do, set the server configuration and check the server logs (queries are executed on the server

. Some more information may help. Are these exceptions written to the log ? thrown? stop ... ;except getting these exception in the log . You wrote: do have an idea why we get following exception ... to the log ? thrown? stop anything? In this particular case, the access to the database

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

the persistence provider for logging and error reporting Since: Jakarta Persistence (JPA) 1.0

.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

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

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

; 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

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

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

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

; logger. log (Level.INFO, "begin select for person " + new Date().toString());     ... ;         logger. log (Level.INFO, "end select for person ... ; for(Person person : persons) {         logger. log

Hi, since I switched to 2.8.3_05 from 2.7.6, the ODB log of my app is full of such messages as ... listed in the log . All the listed classes in the ODB log are not existing anymore in my code ... Explorer, I can see those non-existing classes from the log  listed as Entities, but they have 0

suddenly in the log (we always do a doctor in that case but just after some hours ... the context of ObjectDB, i.e. what is your observation regarding ObjectDB operations, exceptions, log , etc. after this happens. support Support Find attached the log oft he last doctor, regarding

to understand with careful output logging to the Glassfish logs , and also with a diagnostic table ... Web App and viewing both the Glassfish output log and the single served JSF page indexTest.xthml ... of one object of class TestDeepValues. On creation the logs show: INFO: RequestBean []: Created: com

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

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

could happen on commit?   Also, when analyzing this problem, we encountered an issue with the logging mechanism. We enabled full logging (logger name="*" level="debug") and logged to a file with limited size. We did not configure a log -archive ( log -archive path="" retain="0"). That caused an 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

about this error 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 ... EmbeddedSystems We can release a new build that will log relevant information to the log

;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

the obj-reflection. log .  I've included all of my java models in the models.zip file. As far as I ... having unexplained exceptions in logs as they tend to bite you in the long term...        Thanks!              Emily excerpt from log : [2019-09

, everything works perfectly. In reflection mode, the objectdb log on debug mode refers to classes ... models, the objectdb logs for both the enhanced and unenhanced versions, and the objectdb.conf ... onto classes that no longer exist?  You can see the classes in the obj-reflection. log . As far

ObjectDB builds that will log relevant findings. support Support If you run build 2.3.3_02 ... will be detected as soon as it is created and related info will be logged . support Support See attached ... ). The system property doesnt seem to have produced any extra logging though - I've checked

that instead of throwing the exception will write information to the log and proceed (ignoring ... and report new log messages that start with: "Unexpected state in removeEntityTracker"   support Support New version of objectdb installed.  Will report back log entries soon. sjzlondon Steve Zara