[
https://issues.apache.org/jira/browse/IGNITE-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548720#comment-16548720
]
Amir Akhmedov commented on IGNITE-9031:
---------------------------------------
[~vkulichenko], the only case it can happen, as I see so far, when
{{ApplicationContext}} which creates {{IgniteSpringBean}} is used as a parent
for another {{ApplicationContext}}. In this case {{ContextRefreshedEvent}} from
child will be propagated to the parent. This might be a case of Spring MVC
application.
[~langj], can you please share your spring configuration, it will help to
understand the root cause.
> 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
> 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)
