Errors:
Unlocked entities count (1) does not correspond to the number of locked entities (2) for lock 867ddf49-1ce5-4252-b1a6-54d15d4708ed – lexorank issue with duplicate lock id
022-01-19 14:51:12,795 https-jsse-nio-8443-exec-183 [greenhopper.manager.lexorank.LexoRankDaoImpl] ORA-01013: user requested cancel of current operation
java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
Caused by: Error : 1013, Position : 0, Sql = UPDATE "AO_60DB71_LEXORANK" SET "LOCK_HASH" = :1 , "LOCK_TIME" = :2 WHERE "LOCK_HASH" = :3 , OriginalSql = UPDATE "AO_60DB71_LEXORANK" SET "LOCK_HASH" = ?, "LOCK_TIME" = ? WHERE "LOCK_HASH" = ?, Error Msg = ORA-01013: user requested cancel of current operation
Unlocked entities count (1) does not correspond to the number of locked entities (2) for lock 867ddf49-1ce5-4252-b1a6-54d15d4708ed
So when exactly this error is showing? Are you are doing any specific action? Could you list all the steps, or just seeing this in the logs and wondering what is this?
Recommended Learning For You
Level up your skills with Atlassian learning
Atlassian DevOps essentials
Learn how to build, automate, and improve DevOps processes used for the development and delivery of software and other digital products.
Tracking and improving DevOps metrics
Make informed decisions about current and future projects and deadlines to maximize your team's productivity and keep morale high.
Exploring Atlassian Cloud products for agile and DevOps
Coordinate a suite of Atlassian Cloud products for greater collaboration and trust, higher-quality solutions, faster releases, and more.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.