Please update documentation on
https://apacheignite.readme.io/docs/transactions#section-handling-failed-transactions
Andrey.
От: Andrei Aleksandrov
Отправлено: 9 августа 2019 г. в 18:35
Кому: user@ignite.apache.org
Тема: Re: TimeoutException not wrapped in CacheException
Hi,
Sorry, it's my
Hi,
Sorry, it's my fault.
I thought that you get TransactionTimeoutExceptionfrom from some
IgniteCache method. So it's not expected there.
From commit method you can't get the CacheException of course.
So I guess that you should handle only exceptions that mentioned in Java
Doc.
BR,
As I see In javadocs for org.apache.ignite.transactions.Transaction
/**
* Commits this transaction by initiating {@code two-phase-commit}
process.
*
* @throws IgniteException If commit failed.
* @throws TransactionTimeoutException If transaction is timed out.
*
Sorry fo misprint, test does not check that there are no any way to get
TimeoutException
On Fri, Aug 9, 2019 at 5:55 PM Andrey Davydov
wrote:
> It is a little bit difficult to reproduce. We got unhadled exception on
> pre prod performance test of our system. I will try to reproduce it on
>
It is a little bit difficult to reproduce. We got unhadled exception on pre
prod performance test of our system. I will try to reproduce it on weekend.
You test just check that if you get CacheException then TimeoutException is
inside it, but doesn't check that there are no any way to get
Hi,
It looks strange because even Ignite tests expect that
TransactionTimeoutException will be wrapped in CacheException. For
example IgniteTxConfigCacheSelfTest:
try (final Transaction tx = ignite.transactions().txStart()) {
assert tx != null;
On ignite 2.7.5 I got TransactionTimeoutException not wrapped
in CacheException. If it is normal behaviour and I should catch
TransactionTimeoutException too. My current logic is to
catch CacheException and check CacheException.getCause() if it
was TransactionTimeoutException.
Thanks.
Full
