Radek Felcman
Radek Felcman
Sorry I don't understand Your comment about: ``` ``` These properties are for the script output and generated by EclipseLink. Not as the input to generate DB schema. Properties ```...
> Java records are not valid entities. So the results are implementation specific and may vary. Try classes instead of records. It is part of Jakarta Persistence 3.2 https://deploy-preview-652--jakartaee-specifications.netlify.app/specifications/persistence/3.2/jakarta-persistence-spec-3.2-draft01#a487 2.6....
Sorry but I don't see any issue there. My testing project throws expected exception `java.lang.IllegalArgumentException` for code ``` ... TestEntityMaster entity = em.find(TestEntityMaster.class, ID); em.detach(entity); assertFalse(em.contains(entity)); em.remove(entity); ... ``` [jpa-bug-1740-EntityManagerImplCanRemoveDetached.tar.gz](https://github.com/eclipse-ee4j/eclipselink/files/10508911/jpa-bug-1740-EntityManagerImplCanRemoveDetached.tar.gz)
Hello, I checked and tested attached test case and I have to confirm described behavior. About questions above: Questions: --- Is there a way to either use another, more efficient...
> Hello @rfelcman, > > did you have time to consider the changes I proposed in my comment? If so, do you think it is possible to implement them or...
Hello, this change #2228 was due issue issue #1970 , but into 4.x branch was merged yesterday (08-AUG-2024). It's not part of already released 4.0.4 . Master branch is 5.x...
Maybe try latest snapshot from https://jakarta.oss.sonatype.org/content/groups/staging/org/eclipse/persistence/eclipselink/4.0.5-SNAPSHOT/ .
Could You please provide complete stack trace, or at least into `EntityManager` calls. Described case above looks like, that same instance of the `EntityManager` is shared across multiple threads which...
Hello, in the attachment You can find initial test project which is passing now (simple test with one thread). It's based on Apache Derby (in-memory mode) which is automatically started...
I'm continue to check and understand this issue, but what sounds me strange is. How two/multiple threads should "fight" for same instance lock/unlock of the `org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor#instanceLock`? On the begining from...