You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Korol (Jira)" <ji...@apache.org> on 2021/08/04 08:40:00 UTC
[jira] [Updated] (IGNITE-15245) JDBC connection leak with
cache.invoke() over write behind cache store
[ https://issues.apache.org/jira/browse/IGNITE-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Korol updated IGNITE-15245:
--------------------------------
Description:
Given following snippet:
{code:java}
try (Transaction tx = ignite.transactions().txStart(TransactionConcurrency.PESSIMISTIC, TransactionIsolation.REPEATABLE_READ)) {
cache.invoke(pojo.getId(), entryProcessor, pojo);
tx.commit();
}
{code}
If we run this over the cache that uses external storage (e.g. mysql)
> JDBC connection leak with cache.invoke() over write behind cache store
> ----------------------------------------------------------------------
>
> Key: IGNITE-15245
> URL: https://issues.apache.org/jira/browse/IGNITE-15245
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.10
> Reporter: Ilya Korol
> Priority: Major
>
> Given following snippet:
> {code:java}
> try (Transaction tx = ignite.transactions().txStart(TransactionConcurrency.PESSIMISTIC, TransactionIsolation.REPEATABLE_READ)) {
> cache.invoke(pojo.getId(), entryProcessor, pojo);
> tx.commit();
> }
> {code}
> If we run this over the cache that uses external storage (e.g. mysql)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)