-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p7256.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
18.x6.nabble.com/transaction-not-timing-out-tp5540p7187.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
data inconsistency.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6685.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
acquired - what is holding it from updating the entries?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6638.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6579.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
)
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6576.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
age in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6574.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
cannot use optimistic in this scenario.
Thanks,
Binti
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6557.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
If in any case commit() is unable to finish, how can we catch that? in an
optimistic transaction, it should not even reach the commit phase using the
2 phase protocol.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6241.html
Hi,
As Dmitriy pointed out, there is no a reliable way to timeout a transaction
once the commit phase has begun.
If there is a chance that your cache store may stall for unpredictable
amount of time, this should be handled within the store and possibly throw
an exception, but this will result in
ored while committing?
> What would cause this issue?
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5934.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5934.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
te.transactions().txStart(TransactionConcurrency.OPTIMISTIC,
> TransactionIsolation.SERIALIZABLE);
> tx.timeout(2*1000);
> orderUpdateLossPreventionCache.remove(entry.getKey());
> tx.commit();
> } catch (IgniteException e) {
> logger.error("Received IgniteException - rolling back transaction", e);
>tx.rollback();
> throw e;
> }
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5725.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com
> <http://nabble.com>.
>
>
>
(TransactionConcurrency.OPTIMISTIC,
> TransactionIsolation.SERIALIZABLE);
> tx.timeout(2*1000);
> orderUpdateLossPreventionCache.remove(entry.getKey());
> tx.commit();
> } catch (IgniteException e) {
> logger.error("Received IgniteException - rolling ba
message in context:
> http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5805.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Denis, did you get a chance to look at this?
any help will be greatly appreciated.
Thanks,
Binti
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5805.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
;
} catch (IgniteException e) {
logger.error("Received IgniteException - rolling back transaction", e);
tx.rollback();
throw e;
}
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5725.html
Sent fro
rg.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
> java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> java.lang.Thread.run(Unknown Source)
>
>
>
>
> --
)
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5681.html
Sent
out at
> commit() but here i can see that no matter which point the thread is - it
> never times out.
>
> Appreciate your help,
> Binti
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5656.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5656.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
sepaha wrote:
>
> I will get this out to you shortly. In the meantime could you please explain
> how transaction timeout works? Why does commit block forever?
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/transaction-not-ti
I will get this out to you shortly. In the meantime could you please explain
how transaction timeout works? Why does commit block forever?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5617.html
Sent from the Apache Ignite
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5583.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
/transaction-not-timing-out-tp5540p5583.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
(GridIoManager.java:810)
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540
26 matches
Mail list logo
