[
https://issues.apache.org/jira/browse/IGNITE-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578968#comment-16578968
]
Valentin Kulichenko commented on IGNITE-9031:
---------------------------------------------
[~aakhmedov], change makes sense to me. However, just to make sure: does this
need any synchronization? If {{onApplicationEvent}} method can be called by two
threads concurrently, then the code is not thread-safe. But I would assume that
Spring either always does this in a single thread, or has a sync lock. Can you
please check this and confirm?
> SpringCacheManager throws AssertionError during Spring initialization
> ---------------------------------------------------------------------
>
> Key: IGNITE-9031
> URL: https://issues.apache.org/jira/browse/IGNITE-9031
> Project: Ignite
> Issue Type: Bug
> Components: spring
> Affects Versions: 2.6
> Reporter: Joel Lang
> Assignee: Amir Akhmedov
> Priority: Major
>
> When initializing Ignite using an IgniteSpringBean and also having a
> SpringCacheManager defined, the SpringCacheManager throws an AssertionError
> in the onApplicationEvent() method due to it being called more than once.
> There is an "assert ignite == null" that fails after the first call.
> This is related to the changes in IGNITE-8740. This happened immediately when
> I first tried to start Ignite after upgrading from 2.5 to 2.6.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
