6 | Update is ignored by ObjectDB direct access to fields simplifies code porting and direct JSON parsing. User has 100+ fields |
6 | Many connections possible? and will it makes problem in future? system) and TCP/IP ports (when using client-server mode). support Support |
6 | The server cannot start in CentOS" /> </entities> <schema> </schema> <server> <connection port="6136" max="100" /> <data path |
6 | ObjectDB Enincompatible with Quarkus?> <server> <connection port="6136" max="100" /> <data path="$objectdb/db |
6 | Degrading performance overtime" /> </entities> <schema> </schema> <server> <connection port="6136" max="100" /> <data path |
6 | locks on pure query activities> <server> <connection port="6136" max="100" /> <data path="$objectdb/db" /> <embedded |
1 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)) I appreciate your help - in addition to finding some critical bugs your session of porting from |
1 | Out of Memory - Slow leak? on windows so the options for getting a dump are more limited. I'm hoping to get a port opened |
1 | Query fails with failed to read. we access the embedded ObjectDB from explorer with the C/S connection on port 3333 hgzwicker Hans-Georg |
1 | out of memory error-03-16 07:34:13 #9 server] Server on port 3333 has stopped by 1268@wzbhb101 [2017-03-16 07:44:50 |
