Internal Website Search

1-27 of 27 results

Sync ObjectDB and MySQL

Is there a listener or program that can be used to sync across data from/to MySQL and ObjectDB so that I can use ObjectDB for development and then just make sure MySQL always has the same data? ThreaT Ashton Hogan There are plans to implement such a tool. You may subscribe to this feature request

Database Management Settings

is "true" or "false" ) specifies if a recovery file is used. The sync attribute (whose value is "true" or "false" ) specifies if physical writing is required before commit returns. sync =false ... " ) specifies if recording is used. The sync attribute (whose value is "true" or "false" ) specifies

newbie - lots of exeptions

.objectdb.jpa.JpaQuery.getSingleResult(JpaQuery.java:716) at com.prohire.prohire_ sync .ProhireQueries.getProhireSQL(ProhireQueries.java:81) at com.prohire.prohire_ sync .ProhireDataSyncImplementation.getProhireSQL(ProhireDataSyncImplementation.java:65) at com.prohire.prohire_ sync

Safe Settings

file. Which one is safer to use? I suppose I should turn on sync ="true", right? I already tried playing with both configuration settings with the debugger and I put a breakpoint in FileDescriptor# sync ... on the next time it is opened, if necessary. You don't have to enable sync to avoid database corruption

Objectdb recovery

(disk)? Can setting sync =true (for recovery) help with this issue, how will be the performance ... , but you may lose some operations that have been performed after that point. Enabling sync reduces

Query to find object from element of a contained collection

with sync . I still have few issues with the EntityManager and sync that will be the topic

Glassfish 3.1.2.1 and ObjectDB 2.4.3

.classmodel.reflect.Parser$3.call(Parser.java:296) at java.util.concurrent.FutureTask$ Sync .innerRun ... $ Sync .innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java

Failed to generate dynamic type objectdb.java.util.ArrayList

) at java.util.concurrent.FutureTask$ Sync .innerRun(Unknown Source) at java.util.concurrent.FutureTask ... .java:278) at java.util.concurrent.FutureTask$ Sync .innerRun(Unknown Source) at java.util.concurrent

Problem undeploying Glassfish3.1.1 web application cleanly

.call(Executors.java:441) at java.util.concurrent.FutureTask$ Sync .innerRun(FutureTask.java:303

Update entity without first opening a transaction

Hi everyone, I want to update an entity in my program without having to open a transaction, do the modifications and commit the transaction. I want to have a managed entity that is in sync with my database. So when I got a Person class and I do person.setName("John"), the name in my database

High availability and other pratical questions

geo locations/data centers) using some data sync mechanism between them.   Now that i've met

Starting Explorer programmatically

have to manually sync the versions.   Thanks   dmoshal David Moshal This requires changes

Embedded and autosync

. Our question is will these 10 embedded objectDBs be in- sync . E.g.: If a user has logged into box 1

OptimisticLockException

made to the reference are also made to the original instance, hence always in sync ? I could likely

Apache Tomee 1.5.2: Failed to use JTA (TransactionManager is not found)

.util.concurrent.FutureTask$ Sync .innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run

Async query ObjectDb

1. Is it possible to run async objectDb queries for long time operations and stop them if it necessary? 2. Is it possible to stop sync ObjectDb query from another thread for long time operation for example getResultList()? Link to Java API: https://docs.oracle.com/javase/7/docs/api/java/sql

Replication issue, Replayer failing due to NullPointerException.

this? bensteele Ben Steele I should add this causes the replicated database to be out of sync

Redeployment in GlassFish - Failed to open file

.call(Executors.java:441) at java.util.concurrent.FutureTask$ Sync .innerRun(FutureTask.java:303) at java.util

Time Sequence Object Command DB

;Appending has a huge advantage in keeping replicated databases in sync : you need only append new

com.objectdb.o.InternalException

@server [2016-07-13 22:58:15 #2 type] Type com.gsi. sync .Connection.OperationData is not enhanced. [2016-07-13 22:58:16 #3 type] Type com.gsi. sync .FileInfo is not enhanced. [2016-07-13 22:58:17 #4 type] Type com.gsi. sync .FileInfoZip is not enhanced. [2016-07-13 22:58:17 #5 type] Type com.gsi. sync

cannot delete objects after crash (see issue 2283)

Hans-Georg Zwicker You are using recovery in sync ="false" mode: In this mode, commit returns ... always be able to complete a full recovery. Only  sync ="true" guaranties that the recovery ... Zwicker File sync is a slow operation so this is expected. Although we cannot improve the speed

NullPointerException using with "refresh" method

configuration. If it set to sync ="false" (default, for faster operation) you may want to try  sync ="true ... , also with  sync ="true". Is this a problem with the most recent version? Shall I switch back to 2.8.1_01 ... information. If the database is not corrupted then it is not related to sync , and we have to look

database corrupt

. One possible cause is not using sync in the objectdb.conf, which we may have discussed in the past. Using sync =false is faster but less safe (at least with some types of hardware), if objectdb is suddenly ... before starting to write to the database file. Although the default,  sync ="false

NullPointerException on initial database creation

:471) at java.util.concurrent.FutureTask$ Sync .innerRun(FutureTask.java:334) at java.util.concurrent

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

1 - EXTENDED requires a Stateful session bean I apologise that our exchange got out of sync , and I

ObjectDB 2.7.5

Improved recovery from failure when recovery is enabled with no sync   ( issue #2293 ). Added support of using JDO listeners with JPA EntityManager. Added debug logging got persist cascading ( issue #2299 ). Fixed a bug in restricting server access to a range of IPs ( issue #2292 ). Fixed

Named Query Exception

.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$ Sync .innerRun