You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Peter Suppan (JIRA)" <ji...@apache.org> on 2015/02/13 21:58:11 UTC
[jira] [Closed] (OPENMEETINGS-1179) Double email invitations /
simple mail and ics mail invitations
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Suppan closed OPENMEETINGS-1179.
--------------------------------------
Resolution: Not a Problem
testing error by myself - sorry ;-)
> Double email invitations / simple mail and ics mail invitations
> ---------------------------------------------------------------
>
> Key: OPENMEETINGS-1179
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1179
> Project: Openmeetings
> Issue Type: Bug
> Components: UI
> Affects Versions: 3.0.3
> Environment: CentOS 7 on VSP
> Reporter: Peter Suppan
> Assignee: SebastianWagner
>
> Each invitation mail is sent twice. I found this issue recorded in former versions of OM but I am facing that problem now in 3.0.3.
> If a calender entry is made or removed, the participants get each mail twice. The behaviour can be watched in red5 debug mode too - seems the handler is called twice. Please see below.
> -------------
> DEBUG 02-13 20:16:42.335 MailHandler.java 89167 249 org.apache.openmeetings.mail.MailHandler [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-3] - resetSendingStatus enter ...
> DEBUG 02-13 20:16:42.405 MailHandler.java 89237 253 org.apache.openmeetings.mail.MailHandler [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-3] - ... resetSendingStatus done.
> DEBUG 02-13 20:16:42.434 MailHandler.java 89266 258 org.apache.openmeetings.mail.MailHandler [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - sendMails enter ...
> DEBUG 02-13 20:16:42.454 MailHandler.java 89286 260 org.apache.openmeetings.mail.MailHandler [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - Number of emails in init queue 1
> DEBUG 02-13 20:16:42.497 MailHandler.java 89329 218 org.apache.openmeetings.mail.MailHandler [taskExecutor-1] - Message sending in progress
> DEBUG 02-13 20:16:42.498 MailHandler.java 89330 219 org.apache.openmeetings.mail.MailHandler [taskExecutor-1] - To: xxx@xxx.de
> DEBUG 02-13 20:16:42.498 MailHandler.java 89330 220 org.apache.openmeetings.mail.MailHandler [taskExecutor-1] - Subject: New OpenMeetings conference: New Event 17.02.2015 20:16:00 MEZ (+0100) - 17.02.2015 21:16:00 MEZ (+0100)
> DEBUG 02-13 20:16:42.498 MailHandler.java 89330 182 org.apache.openmeetings.mail.MailHandler [taskExecutor-1] - getMimeMessage
> DEBUG 02-13 20:16:42.498 MailHandler.java 89330 144 org.apache.openmeetings.mail.MailHandler [taskExecutor-1] - getBasicMimeMessage
> DEBUG 02-13 20:16:42.580 MailHandler.java 89412 265 org.apache.openmeetings.mail.MailHandler [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - ... sendMails done.
> DEBUG 02-13 20:16:42.581 MailHandler.java 89413 218 org.apache.openmeetings.mail.MailHandler [taskExecutor-2] - Message sending in progress
> DEBUG 02-13 20:16:42.581 MailHandler.java 89413 219 org.apache.openmeetings.mail.MailHandler [taskExecutor-2] - To: xxx@xxx.de
> DEBUG 02-13 20:16:42.581 MailHandler.java 89413 220 org.apache.openmeetings.mail.MailHandler [taskExecutor-2] - Subject: New OpenMeetings conference: New Event 17.02.2015 20:16:00 MEZ (+0100) - 17.02.2015 21:16:00 MEZ (+0100)
> DEBUG 02-13 20:16:42.581 MailHandler.java 89413 182 org.apache.openmeetings.mail.MailHandler [taskExecutor-2] - getMimeMessage
> DEBUG 02-13 20:16:42.581 MailHandler.java 89413 144 org.apache.openmeetings.mail.MailHandler [taskExecutor-2] - getBasicMimeMessage
> DEBUG 02-13 20:16:43.841 MailHandler.java 90673 100 org.apache.openmeetings.mail.MailHandler [taskExecutor-1] - setMessageBody for iCal message
> DEBUG 02-13 20:16:43.853 MailHandler.java 90685 100 org.apache.openmeetings.mail.MailHandler [taskExecutor-2] - setMessageBody for iCal message
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)