 2 | > 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 |
2 | , isPersisted:=false ... To confirm that the values are lost, I started the explorer and searched ... side) - updates are not applied. Hi, thank you for your quick reply. We don't have bidirectional relationships ... complex environment. It is not easy to reproduce the problem. I started yet ObjectDB in Client-Server |
2 | ;
private static BorderPane rootLayout;
@Override
public void start(Stage stage ... use FXML files for all my UI. The problem I'm describing can happen just by starting and stopping the program in quick succession or after running it for extended time, stopping the program |
2 | .setFirstResult(start).setMaxResults(count).getResultList(); is quite slow. Well, after first request ... .hplxtool.dao.impl.ProductDAOImpl - Start: 250, count: 50
2011-11-15 19:31:03.219 [http-bio-8080-exec-3 ... . Thank you for this bug report. New build works great! Thanks for quick fix :) lwalkowski |
2 | 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 |
2 | 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 |
2 | .EjbApplication.start(EjbApplication.java:166)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:122)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:291)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:352)
at com.sun.enterprise.v3.server |
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 | down at around 9:30, then we did increase RAM and cores Did the issue start at 7:03? The first thread dump ... that you had in the past required a quick response (and you couldn't usually wait the 2-3 days average response |
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 |