Internal Website Search
51-60 of 89 resultsRefreshReplication error on slave restart="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities> < ... always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> | |
Replication issue, Replayer failing due to NullPointerException.;cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays ... " /> <dirty-tracking arrays="false" /> </entities> <schema> </schema | |
PersistenceException: Failed to locate field; <cascade-persist always = "true" on-persist = "true" on-commit = "true"/> <dirty ... " on-commit = "true"/> <dirty-tracking arrays = "true"/> < | |
Items in list are doubled, when the entity class is not enhanced with enhancement - but the difference is that when using enhancement - an entity doesn't become dirty just ... and was changed in order to fix orphan removal). If Customer is not dirty | |
Update Entity references if we change the type of an entity will be marked as dirty and changes will be committed. So after the database update your application | |
Connection is closed Caused by: java.io.EOFException; <dirty-tracking arrays="false" /> </entities> <schema> </schema> | |
virtual servers and one filevirtual servers and one file | |
cache optimizing> <dirty-tracking arrays="true" /> | |
Intermittent Server Shutdowns Due to Out of Memory (OOM) Issues" /> <dirty-tracking arrays="false" /> </entities> <schema> | |
javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName That's ok. No problem. Build 2.2.6_01 included a dirty and quick fix that used |