[Sequoiadb-discuss] the controller dead when another controller was closed

[li j. <dis...@gm...>]

Hi All,
   I'm using Sequoia 2.10.10 with derby 10.4.1.3, and have two controllers
in a cluster, and each controller has four virtual databases.  the problem
is when I try to close one controller, then the other one will become dead
lock sometimes(not always). from the recovery log, I found that the dead
lock is caused by incomplete transaction, the last record in recovery log
was an update statement but not "commit" record after that(has "begin"
record before the update statement), is there anyone know the reason? thanks
very much!
Best Wishes!

-- 
Don't schedule every day, make them disorder.