|
I am encountering an issue that email notifications are only going for To Dos and meeting requests otherwise no email is sent for any project, task, issue etc. I have downloaded the new version and updated the application but still emails are not coming to the address except the notification for meetings and to do. After upgrading emails of task created/updated 3-4 days ago are coming now and at specific time that is in between 17:50 – 18:00 hrs. |
|
Teamwork version 4.7.25010 contains a bug that prevented Teamwork to send e-mail notifications. This bug has been solved in the last release. If you are receiving now the old e-mail, is because in Teamwork events have been generated also in the period when notifications did not work. Now that e-mail are sent again, Teamwork is sending also the old ones. To check when your notifications are sent, you have to take a look at the scheduler (admin -> scheduler monitor). if you edit the Job "EmailmessageDispatcher" you will see when the job runs. |
|
Where are the logs for this kept? When I first upgraded a few thousand emails went out before I knew to purge them out. Since then, nothing. I've restarted teamwork. I've disabled / enabled the EmailmessageDispatcher job. I've executed "Run Now" on the job. Nothing is working. I see messages in olpl_message table and nothing is going out. I don't see much for logs but I do see this in my catalina.out log: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Any help is appreciated. |
|
To check if there Teamwork errors, open the platform.log file, you can find it here: TEAMWORK_ROOT/webapps/ROOT/WEB-INF/log post here a significant part of it and I will try to help you! |
|
Under log settings I have "email level" set to "all". I cleared logs. Start teamwork. / Job list / EmailMessageDispatcher / Run Now. Nothing new is added to the log when running EmailMessageDispatcher. The following lines are the only thing present in the platform.log (which were added at startup). ls -altotal 40 drwxr-sr-x 3 root staff 16384 Dec 23 07:34 . drwxr-sr-x 7 root staff 4096 Dec 13 09:44 .. -rw-r--r-- 1 root staff 0 Dec 23 07:34 email.log -rw-r--r-- 1 root staff 0 Dec 23 07:34 hibernate.log -rw-r--r-- 1 root staff 0 Dec 23 07:34 i18n.log -rw-r--r-- 1 root staff 0 Dec 23 07:34 jobLogger.log drwxr-sr-x 2 root staff 16384 Dec 13 09:20 old -rw-r--r-- 1 root staff 4028 Dec 23 07:36 platform.log -rw-r--r-- 1 root staff 0 Dec 23 07:34 proxool.log 2011 Dec 23 07:36:17 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 23:59:59 - 2051 07 18 23:59:59 2011 Dec 23 07:36:18 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 23:59:59 - 2050 01 31 23:59:59 2011 Dec 23 07:36:19 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 23:59:59 - 2051 03 07 23:59:59 2011 Dec 23 07:36:21 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 23:59:59 - 2051 08 09 23:59:59 2011 Dec 23 07:36:25 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 07 18 23:59:59 2011 Dec 23 07:36:26 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 07 18 23:59:59 2011 Dec 23 07:36:26 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 01 31 23:59:59 2011 Dec 23 07:36:27 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2050 01 31 23:59:59 2011 Dec 23 07:36:28 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 01 31 23:59:59 2011 Dec 23 07:36:29 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 02 21 23:59:59 2011 Dec 23 07:36:30 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 07 11 23:59:59 2011 Dec 23 07:36:30 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 03 07 23:59:59 2011 Dec 23 07:36:31 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 02 21 23:59:59 2011 Dec 23 07:36:31 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 07 18 23:59:59 2011 Dec 23 07:36:32 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2041 04 25 23:59:59 2011 Dec 23 07:36:33 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2041 03 08 23:59:59 2011 Dec 23 07:36:33 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 08 15 23:59:59 2011 Dec 23 07:36:34 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 02 21 23:59:59 2011 Dec 23 07:36:35 ERROR platformLogger:237 - getWorkingDaysCountInPeriod for a period with more then 10000 days -> forcing return 10000; period id=null; time interval 2011 12 23 07:36:24 - 2051 08 09 23:59:59 |
|
If email configuration is correctly filled try this. Go in your option and check "notify me events generated by myself ". Then go on a task on which you are assigned and check if you have the "issue added" notification checked on e-mail column. If yes, go to add a new issue to this task. Let me know if you receive this e-mail notification and check if your email.log file contains some errors TEAMWORK_ROOT/webapps/ROOT/WEB-INF/log |
|
That allowed me to receive new alert emails I'm creating now, (though I've only tested a few times). When I look in the DB, however, I perform a select * from olpl_message; and I see 576 messages in that queue (messages from up to a week ago). Any idea why this is? Maybe that messages are for digest, that is sent only once a week. Which is the media for those messages?
(Jan 02 at 09:44)
Silvia Chelazzi ♦♦
|
|
I'm still intermittently missing emails from teamwork. Today I found more than 4000 messages in olpl_message. I found this in the logs (Please advise!): ERROR emailLogger:131 - DigestMessageDispatcher error org.jblooming.persistence.exceptions.StoreException: HibernateFactory store exception saving Message null nul l at org.jblooming.persistence.hibernate.HibernateFactory.store(HibernateFactory.java:76) at org.jblooming.persistence.PersistenceHome.store(PersistenceHome.java:115) at org.jblooming.ontology.IdentifiableSupport.store(IdentifiableSupport.java:126) at org.jblooming.ontology.IdentifiableSupport.store(IdentifiableSupport.java:122) at org.jblooming.messaging.DigestMessageDispatcher.run(DigestMessageDispatcher.java:104) at org.jblooming.scheduler.ExecutableSupport.runAndLog(ExecutableSupport.java:22) at org.jblooming.scheduler.Job.run(Job.java:164) 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.GenericJDBCException: could not insert: [org.jblooming.messaging.Message] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:64) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2345) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2852) at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:71) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:273) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener .java:320) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:203) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.ja va:129) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSav eOrUpdateEventListener.java:210) at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventLi stener.java:56) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEven tListener.java:195) at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java :50) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventLi stener.java:93) at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:713) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:701) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:697) at org.jblooming.persistence.hibernate.HibernateFactory.save(HibernateFactory.java:132) at org.jblooming.persistence.hibernate.HibernateFactory.store(HibernateFactory.java:74) ... 12 more Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'messageBodx' at row 1 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3489) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2542) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1734) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2019) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1937) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1922) at sun.reflect.GeneratedMethodAccessor697.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.logicalcobwebs.proxool.ProxyStatement.invoke(ProxyStatement.java:68) at org.logicalcobwebs.cglib.proxy.Proxy$ProxyImpl$$EnhancerByCGLIB$$557c623f.executeUpdate(<generated
It seems from the log that Teamwork is not able to access a message that has a data too long. I suggest you to clear the olpl_message table (do a complete teamwork database backup before doing it) in this way you will start from a clean situation. If you will get the same error again just write us.
(Mar 14 at 12:20)
Silvia Chelazzi ♦♦
|
