[jira] [Updated] (IGNITE-8522) Transaction incorrect state after cache closed

2018-09-25 Thread Nikolay Izhikov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Izhikov updated IGNITE-8522:

Fix Version/s: (was: 2.8)

> Transaction incorrect state after cache closed
> --
>
> Key: IGNITE-8522
> URL: https://issues.apache.org/jira/browse/IGNITE-8522
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Priority: Major
>
> When we started transaction on client node and closed cache , transaction is 
> rolled back.
> But tx state is still ACTIVE which causes unexpected exception when we try to 
> commit it.
> The expected exception is TransactionRollbackException.
> Look at the following code:
> {code:java}
> public void testTxRollbackWhenCacheClosed() throws Exception {
> startGrid(0);// server node started
> client = true;
> IgniteEx clientNode = startGrid(1);
> IgniteCache cache = clientNode.createCache();// transactional cache 
> is started
> IgniteTransactions transactions = clientNode.transactions();
> Transaction tx = transactions.txStart();
> cache.put(1, 1);
> multithreaded(cache::close, 1);
> tx.commit();// TransactionRollbackException expected, but NPE is 
> thrown.
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8522) Transaction incorrect state after cache closed

2018-09-24 Thread Nikolay Izhikov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Izhikov updated IGNITE-8522:

Fix Version/s: (was: 2.7)
   2.8

> Transaction incorrect state after cache closed
> --
>
> Key: IGNITE-8522
> URL: https://issues.apache.org/jira/browse/IGNITE-8522
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> When we started transaction on client node and closed cache , transaction is 
> rolled back.
> But tx state is still ACTIVE which causes unexpected exception when we try to 
> commit it.
> The expected exception is TransactionRollbackException.
> Look at the following code:
> {code:java}
> public void testTxRollbackWhenCacheClosed() throws Exception {
> startGrid(0);// server node started
> client = true;
> IgniteEx clientNode = startGrid(1);
> IgniteCache cache = clientNode.createCache();// transactional cache 
> is started
> IgniteTransactions transactions = clientNode.transactions();
> Transaction tx = transactions.txStart();
> cache.put(1, 1);
> multithreaded(cache::close, 1);
> tx.commit();// TransactionRollbackException expected, but NPE is 
> thrown.
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8522) Transaction incorrect state after cache closed

2018-06-26 Thread Dmitriy Pavlov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-8522:
---
Fix Version/s: (was: 2.6)
   2.7

> Transaction incorrect state after cache closed
> --
>
> Key: IGNITE-8522
> URL: https://issues.apache.org/jira/browse/IGNITE-8522
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
>
> When we started transaction on client node and closed cache , transaction is 
> rolled back.
> But tx state is still ACTIVE which causes unexpected exception when we try to 
> commit it.
> The expected exception is TransactionRollbackException.
> Look at the following code:
> {code:java}
> public void testTxRollbackWhenCacheClosed() throws Exception {
> startGrid(0);// server node started
> client = true;
> IgniteEx clientNode = startGrid(1);
> IgniteCache cache = clientNode.createCache();// transactional cache 
> is started
> IgniteTransactions transactions = clientNode.transactions();
> Transaction tx = transactions.txStart();
> cache.put(1, 1);
> multithreaded(cache::close, 1);
> tx.commit();// TransactionRollbackException expected, but NPE is 
> thrown.
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8522) Transaction incorrect state after cache closed

2018-05-17 Thread Alexey Kuznetsov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-8522:
-
Fix Version/s: 2.6

> Transaction incorrect state after cache closed
> --
>
> Key: IGNITE-8522
> URL: https://issues.apache.org/jira/browse/IGNITE-8522
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> When we started transaction on client node and closed cache , transaction is 
> rolled back.
> But tx state is still ACTIVE which causes unexpected exception when we try to 
> commit it.
> The expected exception is TransactionRollbackException.
> Look at the following code:
> {code:java}
> public void testTxRollbackWhenCacheClosed() throws Exception {
> startGrid(0);// server node started
> client = true;
> IgniteEx clientNode = startGrid(1);
> IgniteCache cache = clientNode.createCache();// transactional cache 
> is started
> IgniteTransactions transactions = clientNode.transactions();
> Transaction tx = transactions.txStart();
> cache.put(1, 1);
> multithreaded(cache::close, 1);
> tx.commit();// TransactionRollbackException expected, but NPE is 
> thrown.
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)