Hi Timeout with value 9990 is ok because it is just the next step of transaction and 10 ms was spend already for the previous steps of transactions.
On Thu, Feb 23, 2017 at 8:48 AM, bintisepaha <binti.sep...@tudor.com> wrote: > Andrey, > > I finally have an error that might help. this happened again in production > today for us. > Ignite-Console-3.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/n10828/Ignite-Console-3.zip> > > This is the last update that threw an error, after this error every update > just times out. > > The timeout=9990 in this error, none of our transactions have this timeout. > Do you think this is an ignite bug? If you look at the stack trace, this is > not happening due to our code. > > Although there is an error on marshaling. How can we further narrow it down? > > Thanks, > Binti > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Pessimistic-TXN-did-not-release-lock-on-a-key-all-subsequent-txns-failed-tp10536p10828.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
