Home » Eclipse Projects » EclipseLink » Many Warnings from JPA-Added RowIDs When Database Change Notification Enabled(Clean Run without DCN; Almost Every Query Has a Warning )
| Many Warnings from JPA-Added RowIDs When Database Change Notification Enabled [message #1068071] |
Thu, 11 July 2013 22:16  |
 Michel Rainville
Messages: 5
Registered: February 2013 |
Junior Member |
|
|
Windows XP SP3, JDK 6 update 45, Oracle 11g R2, EclipseLink 2.6.0 Nightly Build of July 10, 2013 related to bug report 404473
Does anyone have any suggestions on how to proceed?
It seems that JPA is adding ROWIDs for use in the cache that render most of my queries unusable. I have been trying to disable all caching, because in most cases my small updates are not making it to the database. These updates are sometimes retained across queries of different objects, but not seen by other applications or restarted application itself. If I disable the DCN listener, the application runs normally (except that some changes are not persisted.)
Extract of persistence.xml, which yielded a clean run before the change listener was enabled, and an extract of the Ant log, that includes all the warnings that appeared after DCN was enabled in persistence.xml and in the database,
are both attached.
|
|
|
| Re: Many Warnings from JPA-Added RowIDs When Database Change Notification Enabled [message #1069746 is a reply to message #1068071] |
Tue, 16 July 2013 13:32  |
|
> ORA-01446: cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc.
The error seems to indicate that you have mapped one of your classes to a view instead of a table. It appears DCN cannot work with this view, so you need to disable DCN for this class.
You can do this using the databaseChangeNotificationType of the @Cache annotation,
see, http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Basic_JPA_Development/Caching/DatabaseEvents
Not sure why you are enabling DCN if you just want to disable caching? To disable caching see,
http://wiki.eclipse.org/EclipseLink/FAQ/How_to_disable_the_shared_cache%3F
But caching should have no affect on your updates. Are your updates producing SQL, or the changes not be detected? If they are producing update SQL, then check your transaction configuration, and check if any rollbacks are occurring. If they are not producing SQL, then ensure you are changing managed objects, not detached ones, ensure you are not mixes detached and managed objects, ensure you are maintaining bi-directional relationships correctly, and ensure you are merging your objects correctly. Try debugging your code that is not working.
James : Wiki : Book : Blog : Twitter
|
|
|
Goto Forum:
Current Time: Wed Apr 24 18:34:16 GMT 2024
Powered by FUDForum. Page generated in 0.02849 seconds |
] 
Search
Help
Register
Login
Home
