openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jody Grassel (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (OPENJPA-1901) QueryCacheStoreQuery$CachedObjectId that is not Serializable
Date Mon, 06 Feb 2012 23:38:59 GMT


Jody Grassel resolved OPENJPA-1901.

    Resolution: Fixed
> QueryCacheStoreQuery$CachedObjectId that is not Serializable
> ------------------------------------------------------------
>                 Key: OPENJPA-1901
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 2.0.0, 2.0.1
>            Reporter: Kevin Sutter
>            Assignee: Jody Grassel
>             Fix For: 2.0.3, 2.1.2, 2.2.0, 2.3.0
> In OpenJPA 2.0, OpenJPA tries to put the query result from JOIN query into query cache,
in addition to put entities into data cache.
> However, the QueryResult containes Object[] of org.apache.openjpa.datacache.QueryCacheStoreQuery$CachedObjectId
that is not Serializable and cause this issue.
> OpenJPA need to be fixed to make org.apache.openjpa.datacache.QueryCacheStoreQuery$CachedObjectId
> Currently,  manually adding Serializable to the code works for measuring the performance,
but we need a more permanent fix.
> I also have a concern whether this type of fix has a ripple effect.  The CachedObjectId
can easily be fixed to be Serializable, but it looks like other inner classes of QueryCacheStoreQuery
are not Serializable either.  Do these (and potentially other attributes) need to be Serializable
as well?  Do we need a Unit Test to verify this Serializable capability?
> Final portion of call stack when the Exception happens:
> Caused by: org.apache.openjpa.datacache.QueryCacheStoreQuery$CachedObjectId
> 	at
> 	at
> 	at
> 	at
> 	at java.util.ArrayList.writeObject(
> 	at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at
> 	at
> 	at
> 	at
> 	at

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message