6 | Many connections possible? and will it makes problem in future?My questions is about : 1-) Can objectdb server handle 200.000+ connections at the same time concurrently ? Does it have queue and cache ? 2-) is it dangerous to use that system on many online users ? kadirbasol Kadir BASOL Having 200,000 concurrent threads is probably a bad idea. Usually |
6 | TimeSeries and ObjectDB) - there is no overhead of having each TimeSerie point - in a different entity? The reason is because the parent |
6 | Modifying something with Explorer -> app JPQL with Enum doesn't work anymore can do whatever I want with the application, as long as I avoid Explorer, without having any problem |
6 | Unable to delete the .odb file programatically is having the lock and that is the reason, we are unable to delete the odb file. I have totally 3 odb |
6 | ObjectDB Explorer very slow with remote con. By having just 1 SSH connection to the VPS, it works at an acceptable speed. Sorry and thanks for your reply. zmirc Mircea Chirac |
6 | Recommendation - concurrent access multiple class v of a class. I would really need your advice on this, because having 100% uptime is mandatory |
6 | Objectdb server out of heap space requests is acceptable, but having the whole server die is not (at the very least put in a watchdog process |
6 | Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.xHi, I upgraded the odb file using converter.jar which is having 15943 entry. Previously, with object 1.x, the same query was getting executed within an seconds and now the same is taking around 40 seconds in object db 2.x I have build the query using the follwoing Query query = persistanceManager |
6 | Stalling on "run File" in Netbeans when using -javaagent:lib/objectdb.jar am having problems with a console-based Netbeans Java Application with a nominated Main class to run |
1 | BIRT Driver Improvements about having a runtime driver either integrated in the objectdb jar or (better) available as |
