[
https://issues.apache.org/jira/browse/IGNITE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-553:
------------------------------------
Description:
As we moving to java8 lambdas, it is impossible to use
{{@IgniteInstanceResource}} in lambdas. As a result, single-jvm ping-pong test
does not work.
Suggested fix:
Introduce a static thread-local field which will be set before processing a
message and will be nullified after message is processed. {{IgniteKernal}}
should check this thread-local in {{readResolve}} and return this instance.
was:
As we moving to java8 lambdas, it is impossible to use
{{@IgniteInstanceResource}} in lambdas. As a result, single-jvm ping-pong
example does not work.
Suggested fix:
Introduce a static thread-local field which will be set before processing a
message and will be nullified after message is processed. {{IgniteKernal}}
should check this thread-local in {{readResolve}} and return this instance.
> Need to improve components serialization to use context ignite instance
> -----------------------------------------------------------------------
>
> Key: IGNITE-553
> URL: https://issues.apache.org/jira/browse/IGNITE-553
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: sprint-2
> Reporter: Alexey Goncharuk
> Fix For: sprint-3
>
>
> As we moving to java8 lambdas, it is impossible to use
> {{@IgniteInstanceResource}} in lambdas. As a result, single-jvm ping-pong
> test does not work.
> Suggested fix:
> Introduce a static thread-local field which will be set before processing a
> message and will be nullified after message is processed. {{IgniteKernal}}
> should check this thread-local in {{readResolve}} and return this instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
