2 | ODB IndexActivation NullPointerException) * Batch ended at 88 I've read that: "Indexing large amount of data may take considerable processing time ... please check if the connection time to the database affects. If the database is closed before building the index is completed then the work is discarded and another attempt is done next time. So maybe |
1 | Occasionally slow requests in load testing response times from the DB, around 10 - 15 seconds. Looking at the DB server process with AppDynamics ... - execution time may also be much longer than 10-15 seconds. The other stack trace (com.objectdb.o.PGC:w: line ... and is slow in others. Also, the slow response times occur in wide variety of different queries. I |
1 | Modifying something with Explorer -> app JPQL with Enum doesn't work anymore. In this case rerunning the project many times doesn't help at all. Problem: the number of entities ... or a standalone class. Part-time solution: run the project twice after the modification ... , because sometimes it doesn't work, but you don't know. It's the second time when I encounter this bug in 2 |
1 | Failed to synchronize replicated database and saw It seems to me, that after first start it will create a copy of current state as some basepoint (which is also taking quite lot of time on bigger files :-)) And then it is recording ... . if the slave was down). support Support So there is not currently an API that would allow us to cleanup old |
1 | Pessimestic Locking doesn't release when application unexpectedly terminates. (which is currently not implemented) is to use pessimistic locking with expiration time. For example ... of the current pessimestic lock abruptly quits without releasing the lock it doesn't get released ... resuming of a failed connection by the client. Currently in case of a failed connection the server |
1 | Master database switching to read-only mode, possibly caused by slave failure have synchronised time. > As you know, master failure currently requires manual intervention to get out of READ ... of events was: 13:20 - our monitoring reported GC time per minute on the SLAVE instance over 30 seconds. The GC time on the slave instance continued to grow rapidly until it reached almost 1 minute |
0 | Use temporary files to enable very large transactions the current transaction after creation. Unfortunately, we will receive an OutOfMemory exception ... results), currently the size of a transaction (i.e. the total size of database pages ... ). However, if you are interested in a quick solution, we may be able to increase the current |
0 | javax.persistence.EntityManagerFactory EntityManager. This method returns a new EntityManager instance each time it is invoked. The isOpen ... returns a new EntityManager instance each time it is invoked. The isOpen method will return true |
0 | javax.persistence.Enumerated: public enum EmployeeStatus {FULL_TIME, PART_TIME, CONTRACT} public enum SalaryRate |
0 | Query fails with failed to read2-3 times per day we have a query that fails with: Failed to read from file 'F:\Hummingbird ... . Are you using online backup when the exception is thrown? Any other special activity at that time ... your application). support Support we have it now 5-10 times per day. There is not any backup activity |
