ObjectDB ObjectDB

Internal Website Search

11-20 of 200 resultsRefresh
107

Problem with log file in an embedded db with netbeans platform application

\Ce\Desktop\ProteoB\ProteoApp\build\cluster\modules\ext\log\odb20110921.log (The filename, directory ... \ProteoB\ProteoApp\build\cluster\modules\ext\log\odb20110921.log'     at com.objectdb.o.MSG.d(MSG ... "/>         </properties>     </persistence-unit> It seems that the objectdb logging, that occurs only when I run
106

Failed to write to ObjectDB log file

I get an Error message: Failed to create a new file 'file:C:\Programme\Cytoscape_v2.8.3\plugins\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
105

$temp property not evaluated properly when used in log path

I have the following lines in my objectdb.conf file: <log path="$temp/ObjectDB/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$temp/ObjectDB/log/archive/" retain="90" /> I ... "$temp" in the same directory as my execution script. Shouldn't this be logging to the system temp
104

Undeployment of an remote Glassfish application locks objectdb log file

forget to set an admin password on the Glassfish server and enable "secure admin". Now, log in remotely ... " error message. Because the "odbxxxxxx.log" file is in use by an java process. If I restart Glassfish, I ... a log file in an external directory (not in the web application under Glassfish)? support Support I
103

ClassNotFoundException messages in the log file

In the ObjectDB log file, I still see one ClassNotFoundException. Is this to be expected, or do I have another issue I need to correct? [2017-11-03 13:52:01 #18 type.loader] java.lang ... when logging is enabled at DEBUG level. You can reduce the logging level of "type.loader" to WARNING
103

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 ... It is the normal behavior when using debug level logging globally. But you can decrease logging level
103

Failed to create a new file 'target\objectdb\log\archive' (error 112)

\objectdb". The folder "target\objectdb\log" does not exist yet. Do we have to create ... to create a new file 'target\objectdb\log\archive' (error 112) [11:47:18]: [com.rbccm.felix ... Calculation Services You may try the new build, 2.5.1_03, which should create the log directory
21

message: RetrievalTask in log

the log: ... [2019-03-01 11:53:40 #5 store] RetrievalTask.reportPrimaryResult0: page#27184134, reader.getPos() = 816 ... what does that mean, what to do ? hgzwicker Hans-Georg Zwicker This logging information is written in addition to throwing an exception. Do you see that exception in the log? Maybe
21

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
20

log entry and massive performance issues

) - 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 when the slow

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support