I've asked this before, but I didn't get a reply.
We're getting a huge amount of double locks as shown below:
2007-07-17 16:57:36,408 FATAL DatabaseBackend.ssnen.pgcont1 Double locks
entry:
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED] and
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
java.lang.Exception
at
org.continuent.sequoia.controller.loadbalancer.tasks.AbstractTask.setLocks(AbstractTask.java:451)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.moveMultipleWriteLocksQuery(BackendTaskQueues.java:724)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.checkForPriorityInversion(BackendTaskQueues.java:615)
at
org.continuent.sequoia.controller.loadbalancer.BackendTaskQueues.completeStoredProcedureExecution(BackendTaskQueues.java:1365)
at
org.continuent.sequoia.controller.loadbalancer.tasks.CallableStatementExecuteTask.executeTask(CallableStatementExecuteTask.java:121)
at
org.continuent.sequoia.controller.loadbalancer.tasks.AbstractTask.execute(AbstractTask.java:140)
at
org.continuent.sequoia.controller.loadbalancer.BackendWorkerThread.run(BackendWorkerThread.java:197)
We're using 2.10.8, and I've had a look around and although there is one
mention in JIRA as a Double lock problem being fixed in 2.9.1, but this
doesn't seem the same. What are the cicumstances when this occurs?
Thanks
John
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
