repeated exception in log about releasing lock

[alex_lu]

Hi there,

I'm migrating to alfresco 4 community. I'm getting this exception repeatedly in the log. Has anyone seen this before?

2012-02-28 14:52:52,011  INFO  [activities.feed.AbstractFeedGenerator] [DefaultScheduler_Worker-10] Lock released: {http://www.alfresco.org/model/system/1.0}ActivityFeedGenerator, lock token null
2012-02-28 14:53:06,955  DEBUG [repo.transaction.RetryingTransactionHelper] [JobLockService1] 
Transaction commit failed: 
   Thread: JobLockService1
   Txn:    UserTransaction[object=org.alfresco.util.transaction.SpringAwareUserTransaction@2494c49d, status=0]
   Iteration: 0
   Exception follows:
org.alfresco.repo.lock.LockAcquisitionException: 01280020 Failed to release lock '{http://www.alfresco.org/model/system/1.0}activityfeedgenerator' using token '1c4b0af0-448b-4876-af59-6087b11a8e6d'.  The lock has expired and been taken by another process.
   at org.alfresco.repo.domain.locks.AbstractLockDAOImpl.updateLocks(AbstractLockDAOImpl.java:218)
   at org.alfresco.repo.domain.locks.AbstractLockDAOImpl.releaseLock(AbstractLockDAOImpl.java:172)
   at org.alfresco.repo.lock.JobLockServiceImpl$3.execute(JobLockServiceImpl.java:428)
   at org.alfresco.repo.lock.JobLockServiceImpl$3.execute(JobLockServiceImpl.java:425)
   at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:388)
   at org.alfresco.repo.lock.JobLockServiceImpl.releaseLock(JobLockServiceImpl.java:432)
   at org.alfresco.repo.lock.JobLockServiceImpl$2.run(JobLockServiceImpl.java:352)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:619)


‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

[mrogers]

That's a DEBUG statement, its perfectly normal.

[alex_lu]

Doesn't mean something's wrong? I know activity feed is running all the time but I never used to see it with 3.4.*.

[mrogers]

No it's normal for locks to time out.

[alex_lu]

I see. Thanks lots.

[sebgymn]

I am experiencing the same issue and these debug statements are overloading our log and we want to close these statements. However it is already marked as "warn" level in root log4j.properties file, however it is still spamming debug statements.

Any way to turn it off?

Thanks.

[wgonzalez]

I am experiencing the same issue and these debug statements are overloading our log and we want to close these statements. However it is already marked as "warn" level in root log4j.properties file, however it is still spamming debug statements.

Any way to turn it off?

Thanks.

use the "OFF" level – defined in: http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html#TRACE