 1 | that you a least make the Quick Start also for JDO. However, as I am not buying a license .... By ... reason to use JDO, I'm going to take that probably good advice (above). I've also since starting |
1 | more and more starts executing a simple select query are hanging) Thank you for this report. In order ... ? It may help to identify the exact build in which this issue is started. 2.7.3 works well and 2.7.4_02 doesn't ... we have several times a day the situation that a normal select query is blocking everything A quick |
1 | > Test_Connection: connected 03> UI: start query [query for all object Goods successfully] 04> SELECT u ... 07> UI: start printing result 08> code= A, desc= Good A, byUser= test 09> code= B, desc= Good B ... created [create Goods D successfully] 13> UI: start query [query for all Goods D successfully] 14 |
1 | in the class, but not relevant to the problem. A query like this causes the java process to start ... to be present in 2.5.1_04. Thank you very much for your quick response on this issue. Best regards Emil prolancer |
1 | .StandardContext.startInternal(StandardContext.java:5179)
at org.apache.catalina.util.LifecycleBase.start ... of objectdb.jar. Thanks for such a quick reply. That's one of the main reasons I love ObjectDB |
1 | . In many cases (not always) a user can isolate the problem quite easily by starting from the failed ... didn't work. You can report a problem with no test case of course - but don't expect a quick fix in |
1 | we use spring to start everything. If I do:
System.out.println("EntityManager Name: " + em.getClass ... this case. Hi, Thanks for the quick investigation. That has indeed fixed that issue |
1 | to try running the Maven version of this tutorial. Thank you for your quick reply. But thats a maven ... -repository for this? You are right, this requires a better solution. Starting build 2.6.2_02 |
1 | , and it has been like that for 1 year, since I started using ObjectDB. I'm also accessing from Europe ... for your quick fix, which is what we all now expect from you, as normal. :) We think we found two issues |
1 | . No problem. Build 2.2.6_01 included a dirty and quick fix that used get as a prefix for both get and set ... well. Starting build 2.6.4_03 Enhancer generated hidden methods will have a __odbHidden_ prefix |
