|
We're being bombarded by multiple email alerts from teamwork - literally every 2 minumtes. we've changed all our projects to a future end date - and teamwork continues to send 'overdue emails'. We've also reset the role subscriptions to not send any email alerts - but still the emails come! Help! what can be done? |
|
Probably the cause of this problem is that you have the queue of message full, to solve your problem you should remove the content of the Teamwork table called "olpl_message". Before removing all its rows do a backup of your Teamwork database. if After this operation you still receive message please post here a significant part of the log file: TEAMWORK_ROOT/webapps/ROOT/WEB-INF/log Maybe it contains something that can help me understand your problem. |
|
Hi Silvia I tried deleting the contents of olpl_message and it didn't work - it was better for a little while, but it's now getting worst as we go! Which log file do you want extracts from? You can choose from: email, hibernate, i18n, jobLogger, platform, proxool and schemaHistory. |
|
Hi Silvia Here is a sample row from the olpl_messages table: |
|
If after deleting the content of the olpl_message table Teamwork continues sending you email it means that Teamwork is generating them too often. By default the job that generates messages for expired task runs once every 12 hours and the job which sends digest messages runs once a week. have you changed this value? Please post here a part of the platform.log file. |
|
The last block from the email log: It says "Problem sending e-mail", but we are most definatly getting emails! |
|
Here is the last block from platform.log |
|
Hello Siliva and hello Caroyln, we are facing the very same problem - and haven't solved it for over a year now (OK, I gave up searching a solution a couple of months ago). But now, that I see that we are not the only ones who have this kind of problem, I'll give it one more try! :-) Symptoms are very similar to what you - Carolyn - have described above. This our platform.log has quite the same error passages, e.g. like this: 2010 Dec 28 00:48:19 ERROR emailLogger:81 - Problem sending e-mail
org.jblooming.PlatformRuntimeException: Server time: 2010 12 28 00:48:19. from com.twproject.resource.Person as p where p.myself.id=:twopid
Server time: 2010 12 28 00:48:19.
The exception thrown:
at org.jblooming.oql.OqlQuery.uniqueResult(OqlQuery.java:86)
at com.twproject.operator.TeamworkOperator.getMyPersonFromPersistence(TeamworkOperator.java:90)
at com.twproject.operator.TeamworkOperator.getPerson(TeamworkOperator.java:76)
at com.twproject.operator.TeamworkOperator.getDefaultEmail(TeamworkOperator.java:185)
at sun.reflect.GeneratedMethodAccessor682.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
at org.jblooming.operator.Operator$$EnhancerByCGLIB$$59d507f4.getDefaultEmail(<generated>)
at org.jblooming.messaging.EmailMessageDispatcher.run(EmailMessageDispatcher.java:68)
at org.jblooming.scheduler.ExecutableSupport.runAndLog(ExecutableSupport.java:22)
at org.jblooming.scheduler.Job.run(Job.java:161)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.hibernate.exception.JDBCConnectionException: could not execute query
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.loader.Loader.doList(Loader.java:2216)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
at org.hibernate.loader.Loader.list(Loader.java:2099)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:378)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811)
at org.jblooming.oql.OqlQuery.uniqueResult(OqlQuery.java:79)
... 17 more
Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: No operations allowed after connection closed.
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:980)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926)
at com.mysql.jdbc.ConnectionImpl.checkClosed(ConnectionImpl.java:1098)
at com.mysql.jdbc.ConnectionImpl.prepareStatement(ConnectionImpl.java:4076)
at com.mysql.jdbc.ConnectionImpl.prepareStatement(ConnectionImpl.java:4042)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.logicalcobwebs.proxool.ProxyConnection.invoke(ProxyConnection.java:68)
at org.logicalcobwebs.cglib.proxy.Proxy$ProxyImpl$$EnhancerByCGLIB$$da937545.prepareStatement(<generated>)
at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:505)
at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:423)
at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547)
at org.hibernate.loader.Loader.doQuery(Loader.java:673)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.doList(Loader.java:2213)
... 26 more
What else? In table olpl_message for ALL ROWS the field ANY HELP WOULD BE HIGHLY APPRECIATED - because we are using tw with a disabled scheduler for over a year now, wich is no fun! Thanks very much & regards, Andreas |
|
It seems from the log that you have more than one person associated with the same Operator, you should open your Teamwork database -> table called twk_resources and check if there is more than one row with discriminator = PERSON and with the same value in the column "myself". You should run a query like this: SELECT myself, COUNT(*) as expr FROM twk_resource WHERE (discriminator = 'person') GROUP BY myself post the result of your query here. |
|
Hello Silvia, thanks for trying! But it does not seem like there were persons with the same value in the field myself Count
37
1 1
2 1
3 1
4 1
5 1
6 1
7 1
8 1
9 1
10 1
12 1
13 1
14 1
15 1
16 1
17 1
18 1
19 1
20 1
21 1
24 1
25 1
So there are 37 persons with an empty string in the field Regards, Andreas Hi Andreas, I've tested it but I cannot find the origin of the problem :-( it seems that there is something wrong in the Teamwork database. If you are using Mysql you could send me a backup of it so I can try to help you solving this problem.
(Jan 10 '11 at 11:54)
Silvia Chelazzi ♦♦
|
|
Hello, The same problem is for us and we were unable to fix it. Here is a part of our log: 2011 Lie 15 16:44:31 FATAL platformLogger:23 - from com.twproject.resource.Person as p where p.myself.id=:twopid Server time: 2011 07 15 16:44:31. The exception thrown: org.jblooming.PlatformRuntimeException: Server time: 2011 07 15 16:44:31. from com.twproject.resource.Person as p where p.myself.id=:twopid Server time: 2011 07 15 16:44:31. The exception thrown: |
