ObjectDB Database Search

. This could be caused, for example, if the database is stopped (abnormally) during a writing action, and recovery

osx menu item (for starting/ stopping server, viewing config files, data roots, etc) is extremely useful. However, currently the about box doesn't show the current jar version of the server (and with rapid updates, it's difficult to know which version of the server is currently running, and track

These are not exactly the same errors but maybe related. Errors that stop (even for awhile

These are questions asked in the context of the proposed architecture described in the forum thread titled, "Sample JDO Architecture for Follow Up Questions".   I desire offline backups.  I must close all connections, wait for current database activity to stop , and prevent new

Hi,   AFter the upgrade from 2.2.8_02 (not sure if it was build 03/04 as I skipped 03) - my LIKE queries have stopped working during a regression test. As an example output: Query: SELECT $1 FROM Company $1 WHERE ((($1.companyId LIKE :p1) AND ($1.conditionOne=true)) AND ((($1.conditionTwo

Customer asked during opened ObjectDb connection (ODB location A) to stop writing and continue to another ODB file (Location B). Does exist some API to achieve that? What is a possible solution? Harman Alexander Golyshkin You have to close the database in location A, copy it from location

Hi, how to start objectdb as a service from linux command line. Every time i close the terminal (putty) servers stops . Running it with the & parameter dont help. we are starting the database with this command ./server.sh start Thanks peric.emil Emil Perić How do you start the server, with the run

Running in embedded mode, configuration specifies " ".  Still, tablename.odb$ files get created, and if still present after an abrupt stop , the application will not restart properly.   What do we need to do to not utilize recovery files (not have orphan tablename.odb$ files)? CAPdev CAP

works well), but you will have to be aware and report if it stops working in a future version. support Support

could connect when I stopped my program that embedded the db. Is     still supposed to work

of 3.6GB (used to work with objecdb 1.x) It now stops (outofmemory) when the odb file

. Also the network interface was not changed. But from some moment old activation key stopped working

will be included in the next build . While this should stop the crashes, we want to ensure

stops that unifies the changes in the different EntityManager objects I have created in Main

detected and saved. Am I doing something wrong that may stop working without warning? kjkrum Kevin

by heavy querying of the database.  Once the querying stops , the memory usage never returns

. Currently, to avoid multiple models in the database, I have to undeploy from Glassfish, stop

the test again, we stop the appliaction and then repeat the above.   Explanation

The second setting is expected to stop ObjectDB from returning to a list of fields that was used in

I understand, we'd need to stop the DB, run the Doctor in repair mode and start the DB

.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment Guestbook.war

stops once a day with no apperent reason. Second cause we suspect is the number of network connections

Please let me know why the OS timestamp is changing for the parent folder. How can i stop the timestamp

a modal JDialog which would stop the application so I could attach the profiler, aside from that test

thing is - allocated memory by storage threads stops at the size of database. Maybe there is some

. I cannot get an EntityManager connection to the slave DB though. I've tried stopping both servers

used the File technique already, but it means I have to stop the container to be sure the DB file

one might consider "side-effects". I found on switching to ObjectDB this did not work and stopped the practice completely.     webel Dr Darren Kelly

, we had to stop and run the Doctor. Find attached the latest log   hgzwicker Hans-Georg Zwicker

:34:13 #9 server] Server on port 3333 has stopped by 1268@wzbhb101 [2017-03-16 07:44:50 #10

After an error in a @PrePersist method in an Entity class, the database stopped working. Fortunately this was in development, but still worrying! The Entity class @Entity @Table(uniqueConstraints = {     @UniqueConstraint(columnNames = "personalNumber")}) public class Customer

and disorderly stopped  in the middle of busy transactions. The immediate solution is probably

. support Support I stopped the DB and ran the Doctor over it and it found no errors, however, when I

much more load that doesn't stop . Anyway, the way forward may be optimising the queries, and if duplicate

when Swing is unavailable. Currently start/ stop /restart messages are printed to the standard output

Support again we have an assert (we could only stop and copy the database 2 days ago, there was not

there is another problem that stops the query execution with another exception, but that other exception

Our objectdb server completely stopped responding to requests for new connections. The 'server' command also would not respond. A thread dump (attached) shows a deadlock. FastModel Ben Schreiber Thank you for this report. Build 2.2.9_01 should fix the deadlock. support Support Build 2.3.7_04 fixes

application is stopped ) do you close the ObjectDB database ( EntityManagerFactory 's close), e.g

level logging for indicating server start and stop . Improved error message for creating a query with a closed EntityManager ( issue #1032 ).

the databases, i.e. I let the test run for 20mins; stopped the test; restarted the server; restarted the test

of more than one class path root ( issue #554 ). Fixed a NullPointerException on detachment of some objects. Fixed Linux "Name or service not known" error on server stop .

above database files and it stopped doing it. Sometimes it doesn't help.       thamal

; jastorga Juan This exception is unknown and more information will be needed. Please try to stop the server

existing referenced objects. Fixed a bug in stopping an ObjectDB Server in SSL mode from another process ( issue #1804 ).