AbstractFeedGenerator warning

[dullaertd]

hello,

I have a freshly deployed alfresco 3.0.1 running on Weblogic, that was installed on solaris. For the backend we use Oracle 10g2

When I look in the log files, i keep getting the same warning (shown below). Could some one tell me what this means and perhaps how to resolve it?

10:43:12,912 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
10:51:42,905 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:04:42,917 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:09:42,913 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:13:12,920 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:13:42,920 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:14:12,920 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:24:42,921 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:43:12,908 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:43:42,908 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
11:44:12,907 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
12:05:12,910 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
12:05:47,215 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …
12:06:12,919 WARN  [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Still busy …



Thanx in Advance!

[compaqnx7300]

Did you resolved this problem? I have similar situation. My Alfresco (v. 3.3.0) starts correctly and work correctly for some time. After a few hours two warnings appears:\

WARN  [activities.feed.AbstractFeedGenerator] Still busy …
WARN  [activities.feed.AbstractFeedGenerator] Still busy …
‍‍‍‍

and Alfresco does not respond. It even does not close correctly (I have to force it)

[svast]

+1… I am facing the same issue, after some load test.
Is Alfresco experiencing some dead lock in its transactions?

@developers: On what kind of events this message is thrown?

[kahya]

The same here, but i get the bug only when i use a benchmark tool, not in a comon usage..

[compaqnx7300]

For what is responsible AbstractFeedGenerator?
I noticed, that it happens when system is not used too. I start system, wait about 6-7 hours, warning on console appears and it is not possible to do anything in system 

[kpacierpnik]

Hi,
I have the same problem with Alfresco 3.3. My suspicion is that it's database "deadlock" or "unclosed connections" issue. Did anybody submit it in JIRA?

[kpacierpnik]

I discovered that some  threads are waiting  infinitely while having transaction opened or opening transaction. In my case this situation happens when creating a lot of workflows (10 users creating 1 workflow per 2 seconds).I think that all connections from database connection pool are used, because they are not closed properly.

Example threads:

——————————————————————————————————————————————————————————————-
Name: AlfrescoJbpmJobExecutor:10.0.1.96:1
State: WAITING on org.apache.commons.pool.impl.GenericObjectPool@36961
Total blocked: 0  Total waited: 4

Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:942)
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java:81)
org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:119)
org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57)
org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1326)
org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:555)
org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)
org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:336)
org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:293)
org.alfresco.util.transaction.SpringAwareUserTransaction.begin(SpringAwareUserTransaction.java:411)
   - locked org.alfresco.util.transaction.SpringAwareUserTransaction@bbe1a4
org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:310)
org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:228)
org.alfresco.repo.workflow.jbpm.AlfrescoJobExecutorThread.acquireJobs(AlfrescoJobExecutorThread.java:95)
org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:54)
——————————————————————————————————————————————————————————————-

——————————————————————————————————————————————————————————————-
Name: http-8080-47
State: WAITING on org.apache.commons.pool.impl.GenericObjectPool@36961
Total blocked: 994  Total waited: 995

Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:942)
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java:81)
org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:119)
org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57)
org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1326)
org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:555)
org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)
org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:336)
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:102)
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
$Proxy39.validate(Unknown Source)
org.alfresco.web.app.servlet.AuthenticationHelper.getUser(AuthenticationHelper.java:487)
org.alfresco.web.app.servlet.AuthenticationHelper.authenticate(AuthenticationHelper.java:173)
org.alfresco.web.app.servlet.AuthenticationHelper.authenticate(AuthenticationHelper.java:154)
org.alfresco.web.app.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:99)
sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.alfresco.repo.management.subsystems.ChainingSubsystemProxyFactory$1.invoke(ChainingSubsystemProxyFactory.java:116)
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
$Proxy206.doFilter(Unknown Source)
org.alfresco.repo.web.filter.beans.BeanProxyFilter.doFilter(BeanProxyFilter.java:82)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.alfresco.repo.web.filter.beans.NullFilter.doFilter(NullFilter.java:68)
sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.alfresco.repo.management.subsystems.ChainingSubsystemProxyFactory$1.invoke(ChainingSubsystemProxyFactory.java:116)
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
$Proxy206.doFilter(Unknown Source)
org.alfresco.repo.web.filter.beans.BeanProxyFilter.doFilter(BeanProxyFilter.java:82)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
java.lang.Thread.run(Thread.java:619)
——————————————————————————————————————————————————————————————-

[luisalves00]

I have the same problem…

How to make sure the transactions are properly closed?

[svast]

May it be related to the database layer?

By default Alfresco recommands MySQL. Has everyone here encountered that issue on MySQL also?
Is it occurring on PostgreSQL, or other RDBMS?

Thanks a lot for your feedbacks.

[svast]

FYI : This issue has been reproduced also with postgreSQL backend.