[
https://issues.apache.org/jira/browse/IGNITE-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575745#comment-16575745
]
ASF GitHub Bot commented on IGNITE-9031:
----------------------------------------
GitHub user amirakhmedov opened a pull request:
https://github.com/apache/ignite/pull/4511
IGNITE-9031: SpringCacheManager throws AssertionError during Spring i…
…nitialization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/amirakhmedov/ignite IGNITE-9031
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4511.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4511
----
commit e8c4b0f96c1ee107fbc024caebdd7323ee17bba4
Author: Amir Akhmedov <amir.akhmedov@...>
Date: 2018-08-10T04:25:28Z
IGNITE-9031: SpringCacheManager throws AssertionError during Spring
initialization
----
> 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)
