You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2026/09/24 08:44:00 UTC
[jira] [Updated] (IGNITE-25614) Exception in CacheStoreListener#onSessionEnd can cause inconsistency of CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-25614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgeny Stanilovsky updated IGNITE-25614:
----------------------------------------
Ignite Flags: (was: Release Notes Required)
> Exception in CacheStoreListener#onSessionEnd can cause inconsistency of CacheStore
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-25614
> URL: https://issues.apache.org/jira/browse/IGNITE-25614
> Project: Ignite
> Issue Type: Bug
> Reporter: Ilya Shishkov
> Priority: Major
> Labels: ise
> Attachments: CacheStoreSessionListenerFailureTest.patch
>
>
> {{CacheStoreListener#onSessionEnd}} is invoked during transaction commit.
> In case if we commit state to external database inside {{#onSessionEnd}} and then some exception occurs, then transaction will be rolled back in Ignite, but will not in external database.
> *Reproducer:* [^CacheStoreSessionListenerFailureTest.patch]
> As you can see in attached reproducer, it does not matter, if put fails on primary or backup node.
> Also, {{#onSessionEnd}} is invoked once on initiating node.
> Logic of commit to external database is the same as in [1].
> Also, cache operation raises unexpected {{IgniteException}} instead of {{CacheException}}.
> # https://github.com/apache/ignite/blob/946360aa5438d8fabf0a7df4082ffb83346503ea/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheJdbcStoreSessionListener.java#L125
--
This message was sent by Atlassian Jira
(v8.20.10#820010)