|
[
Permlink
| « Hide
]
Jeff Turner [Atlassian] added a comment - 14/Jul/05 01:10 AM
Please could you attach the JIRA logs. There is generally something in there indicating why the mail queue is hung.
Here are the logs after a restart. Flushing eMail still does not work and no mails are sent automaticly, but sending a test mail works fine.
I just ran into this as well with 3.2.1 Ent. The only relavent information in the log is from seven days before the first message in the mail queue:
2005-06-30 08:25:37,840 ERROR [atlassian.mail.queue.MailQueueImpl] Error occurred in sending e-mail: To='fperez@amicas.com' Subject='Commented: (RIS-2820) Exams with procedures that can be scheduled in different resources =- the Monitors show the exam in the incorrect resource' From='ascott@amicas.com' FromName='Franklin Perez (JIRA)' Cc='null' Bcc='null' ReplyTo='null' InReplyTo='<9840044.1119972489794.JavaMail.SYSTEM@jira>' MimeType='text/plain' Encoding='UTF-8' Multipart='null' MessageId='null' Tom,
Thank you for the log files. I believe they cover the period of time after JIRA has been restrated. Is this so? Next time the problem occurs would you be able to send us the log files taht have been generated before JIRA has been bounced. Joshua, Also thank you for the logs. I beleive all these problem occur due to the fact that the netwrok connecting JIRA to the SMTP server goes doen, or the SMTP server itself. May I ask when this problem occurs if you go to Administartion -> System -> Mail Queue does the queue say that it is sending? For example does the screen say something like: Could you generate a thread dump before rebooting JIRA next time it runs? To generate a thread dump on linux/unix just do a 'kill -3 <pid>' on the JIRA process. On Windows to a CTR+Break on the command window (Tomcat's console). The thread dump shoudl go to the logs or the Tomcat's console. Please send it to us. Thanks,. The attached logs now cover the period after a restart:
1. JIRA worked fine. 2. Maybe the connection to the SMTP server was not available for a short time 3. Notifications and flushing the mail queue don't work 4. Mail queue screen says : Anton, I agree it looks like there might have been an SMTP server outage on 6/30. The earliest message in the mail queue was from 7/7 though. The Mail Queue page did not say that it was sending, and flushing the queue did not work. JIRA is running as a Windows service, I don't know of a way, off hand, of generating a thread dump in that situation.
I could be wrong about the Mail Queue page. Things look stuck again, and it does say "The queue currently has 20 items in it. The mail queue is sending, it started sending at ." The logs do not contain anything looking like the previous SMTP connection errors. In fact, they contain very little beyond a database connection hiccup.
I am going to try what the this article suggests: http://confluence.atlassian.com/display/JIRA/Issues+with+tomcat+4.x+mail+and+activation+jars
Hi,
Thanks you for the details. I believe this problem occurs due to the fact that JIRA does not set a connection timeout on the connection to the mail server. If the mail server goes down while JIRA is communicating with it, the mail queue can hang. We have made a build of the atlassian-mail that should fix the problem available here: Please download the above file and replace the atlassian-mail jar in The jar contains a atlassian-mail.properties file with the following properties: mail.smtp.connectiontimeout=300000 (in milliseconds). This will make the connection timeout after 5 minutes if the mail server is down during the connection or after 10 minutes if the mail server goes down after a connection has been established. Please restart JIRA for the changes to take effect. Please let us know if this helps. Thanks, The advice from the article did not do the trick, as the mail queue was backed up this morning again. I have downloaded the atlassian-mail jar file and restarted the server. Hopefully that will do the trick...
We had no problems since more then a week with with atlassian-mail-1.2.28.jar.
From our point of view you can close this issue. Thanks Tom Thanks for the update!
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||