[
https://issues.apache.org/jira/browse/IGNITE-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225027#comment-16225027
]
Vyacheslav Koptilin commented on IGNITE-6669:
---------------------------------------------
Pull-Request was updated in order to properly handle Write-Behind mode.
TC looks good enough. I have not found test failures that are related to the
fix.
pull-request: https://github.com/apache/ignite/pull/2894
review: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-385
TC:
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2894%2Fhead
> CacheStoreSessionListener#onSessionStart() #onSessionEnd() methods are called
> by GridCacheStoreManagerAdapter even if a store operation should not be
> performed.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-6669
> URL: https://issues.apache.org/jira/browse/IGNITE-6669
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: cache
> Affects Versions: 1.8
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Attachments: Reproducer.java
>
>
> In the case of transactional cache, which is configured using {{CacheStore}}
> and {{CacheJdbcStoreSessionListener}}, every update triggers
> {{CacheStoreSessionListener # onSessionStart()}} that results in creating the
> connection to an underlying database, even if read-through and write-through
> modes are disabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
