Thanks Ivan.
If methodCache is marked as transient, proxied objects are not meant to be
cached. Since this object is returned by spring JPA, hibernate second level
caching might be enough. Looks like we should not cache JPA returned objects
at method level.
--
Sent from: http://apache-ignite-u
Hi daya,
Yes it is a serialization issue. Field AdvisedSupport.methodCache is marked
transient and method readObject which should initialize this field on
deserialization is not called. So, it has value null and NPE is thrown. I
am not sure whether it is expected behavior or not.
Also, it does not
Hi daya,
Sorry for delay. I hope I will have a minute tomorrow to check this case.
On 13.08.2018 15:04, daya airody wrote:
HI Ivan,
I have uploaded a simple spring application reproducing the issue at below
link:
https://github.com/daya-airody/ignite-caching
When I use ConcurrentMapCache to
HI Ivan,
I have uploaded a simple spring application reproducing the issue at below
link:
https://github.com/daya-airody/ignite-caching
When I use ConcurrentMapCache to cache results from spring JPA native query,
I am able to retrieve it correctly. However, once I enable ignite and
JCache, I run
Hi,
Looks like Spring itself wraps result into proxy. If you could provide a
reproducer it will help to find a reason faster.
2018-08-07 21:09 GMT+03:00 daya airody :
> Values retrieved from cache are wrapped with JdkDynamicAopProxy. This
> throws
> below NPEs
>
> ---
> java.lang.NullPo
Values retrieved from cache are wrapped with JdkDynamicAopProxy. This throws
below NPEs
---
java.lang.NullPointerException: null
at
org.springframework.aop.framework.AdvisedSupport.getInterceptorsAndDynamicInterceptionAdvice(AdvisedSupport.java:481)
at
org.springframework.
