The workaround we found (at least for now) is to force DSpace to look into the database instead of using the cache. Doing so doesn't throw an error.
So in file:
[Source]\dspace-api\src\main\java\org\dspace\workflow\WorkflowItem.java
We have added the one more line:
{{public static WorkflowItem find(Context context, int id) throws SQLException { // First check the cache WorkflowItem fromCache = (WorkflowItem) context.fromCache( WorkflowItem.class, id);
-
fromCache = null;* // <= this forces Dspace not to use the cache
if (fromCache != null) { return fromCache; }
}} (...)
I don't know if intervening with the cache is the right approach to solve this problem but it seems to work for us.
|