This is a space where the community of Teamwork users can ask for support, explanations,
and also vote up or down questions, answers and feature requests.
>> Back to Teamwork's site.

Besides a reboot of the sever teamwork runs on nothing has changed on the actual configuration of teamwork and email hasn't worked since. I've tried changing the smtp server just to verify and still no luck.

asked Nov 12 '10 at 11:57

yathink's gravatar image

yathink
361


Restarted scheduler and started working. Thanks

answered Nov 15 '10 at 09:21

yathink's gravatar image

yathink
361

You should post here a significant part of the platform.log file (log) so I can try to understand which is the cause of the problem. You should also check if your scheduler is running. Go in the administration page and click on scheduler monitor. if it is stopped insert in the "tick in seconds" field "5" and then click on start.

answered Nov 15 '10 at 03:37

Silvia%20Chelazzi's gravatar image

Silvia Chelazzi ♦♦
408519

We have the same problem, happens weekly without any notice from the Teamwork system. The Teamwork system ( scheduler ) does not even detect it is broken. It is a serious problem

answered Nov 15 '10 at 22:01

MTG%201's gravatar image

MTG 1
1112

When the scheduler is not running a red message should appear at the end of each Teamwork page. Now we should understand why the scheduler does not restart automatically if you restart Teamwork. Stop teamwork clear the platform.log file and restart it. Check if the scheduler is restarted and if the log contains error.

(Nov 16 '10 at 03:35) Silvia Chelazzi ♦♦

The problem is that the scheduler says it is running however all email and sticky notifications will stop working so no one will receive any messages.

If you go to those jobs and run them manually then everything returns back to normal.

I already sent you some time ago some logs via email

answered Nov 16 '10 at 04:05

MTG%201's gravatar image

MTG 1
1112

2010 Oct 26 03:15:08 ERROR emailLogger:81 - Problem sending e-mail java.lang.NullPointerException at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:599) at org.jblooming.messaging.MailHelper.send(MailHelper.java:464) at org.jblooming.messaging.MailHelper.sendHtmlMail(MailHelper.java:188) at org.jblooming.messaging.MailHelper.sendHtmlMail(MailHelper.java:147) at org.jblooming.messaging.MailHelper.sendHtmlMail(MailHelper.java:138) at org.jblooming.messaging.EmailMessageDispatcher.run(EmailMessageDispatcher.java:75) 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) 2010 Oct 26 03:15:08 ERROR emailLogger:81 - Problem sending e-mail java.lang.NullPointerException at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:599) at org.jblooming.messaging.MailHelper.send(MailHelper.java:464) at org.jblooming.messaging.MailHelper.sendHtmlMail(MailHelper.java:188) at org.jblooming.messaging.MailHelper.sendHtmlMail(MailHelper.java:147) at org.jblooming.messaging.MailHelper.sendHtmlMail(MailHelper.java:138) at org.jblooming.messaging.EmailMessageDispatcher.run(EmailMessageDispatcher.java:75) 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)

answered Nov 18 '10 at 18:25

MTG%201's gravatar image

MTG 1
1112

2010 Oct 31 03:15:08 FATAL platformLogger:243 - java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$KeyIterator.next(Unknown Source) at java.util.AbstractCollection.addAll(Unknown Source) at java.util.HashSet.<init>(Unknown Source) at org.jblooming.scheduler.Scheduler.run(Scheduler.java:189) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) 2010 Oct 31 04:40:08 FATAL platformLogger:243 - java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$KeyIterator.next(Unknown Source) at java.util.AbstractCollection.addAll(Unknown Source) at java.util.HashSet.<init>(Unknown Source) at org.jblooming.scheduler.Scheduler.run(Scheduler.java:189) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) 2010 Oct 31 05:48:08 FATAL platformLogger:243 - java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$KeyIterator.next(Unknown Source) at java.util.AbstractCollection.addAll(Unknown Source) at java.util.HashSet.<init>(Unknown Source) at org.jblooming.scheduler.Scheduler.run(Scheduler.java:189) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)

answered Nov 18 '10 at 18:25

MTG%201's gravatar image

MTG 1
1112

the same problem happened on our teamwork.....

answered Dec 12 '10 at 21:29

StephenWang's gravatar image

StephenWang
111

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

×24

Asked: Nov 12 '10 at 11:57

Seen: 733 times

Last updated: Dec 12 '10 at 21:29

| Teamwork faq | about | contact us | Teamwork blog | Teamwork documentation | feedback always welcome