Hi Everyone,
We have configured the outgoing email (SMTP Server in JIRA), we have updated the Timeout is 10000ms & SMTP port 25.
Configured the email requested for JSD projects support requires via email.
When i check the mail audit log, we found connectivity log and processing log.
I found that every time am I seeing the failure message " Couldn't connect to host, port:outlook.office365.com, 993; timeout 50000.
I want to know why its exactly timeout at 50000.
FYR. Pasted the logs below
2019-05-24 14:20:10,311 ERROR [] Sending mailitem To='prasad@gateway..com' Subject='(EDA-59786) TSG - Jobwork concept need to be enhanced as per TSG Law' From='null' FromName='crmuser (JIRA)' Cc='null' Bcc='null' ReplyTo='null' InReplyTo='null' MimeType='text/html' Encoding='UTF-8' Multipart='javax.mail.internet.MimeMultipart@5926af86' MessageId='null' ExcludeSubjectPrefix=false' anonymous Mail Queue Service Error occurred in sending e-mail: To='purushotham.rn@gateway.greettech.com' Subject='(EDA-59786) TSG - Jobwork concept need to be enhanced as per TSG Law' From='null' FromName='crmuser (JIRA)' Cc='null' Bcc='null' ReplyTo='null' InReplyTo='<JIRA.382909.1498467417000@Atlassian.JIRA>' MimeType='text/html' Encoding='UTF-8' Multipart='javax.mail.internet.MimeMultipart@5926af86' MessageId='null' ExcludeSubjectPrefix=false'
com.atlassian.mail.MailException: javax.mail.MessagingException: Exception reading response;
nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.atlassian.mail.server.impl.SMTPMailServerImpl.sendWithMessageId(SMTPMailServerImpl.java:225) [atlassian-mail-2.8.6.jar:?]
at com.atlassian.mail.queue.SingleMailQueueItem.send(SingleMailQueueItem.java:44) [atlassian-mail-2.8.6.jar:?]
at com.atlassian.mail.queue.MailQueueImpl.sendBufferUnderLock(MailQueueImpl.java:103) [atlassian-mail-2.8.6.jar:?]
at com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:56) [atlassian-mail-2.8.6.jar:?]
at com.atlassian.jira.mail.JiraMailQueue$1.apply(JiraMailQueue.java:51) [classes/:?]
at com.atlassian.jira.mail.JiraMailQueue$1.apply(JiraMailQueue.java:48) [classes/:?]
at com.atlassian.jira.util.velocity.DefaultVelocityRequestContextFactory.runWithStaticBaseUrl(DefaultVelocityRequestContextFactory.java:110) [classes/:?]
at com.atlassian.jira.util.DefaultBaseUrl.runWithStaticBaseUrl(DefaultBaseUrl.java:50) [classes/:?]
at com.atlassian.jira.mail.JiraMailQueue.sendBuffer(JiraMailQueue.java:48) [classes/:?]
at com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:21) [classes/:?]
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:68) [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62) [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44) [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32) [classes/:?]
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153) [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118) [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97) [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:410) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:388) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34) [atlassian-scheduler-caesium-1.3.3.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
Caused by: javax.mail.MessagingException: Exception reading response;
nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:2369) [javax.mail-1.5.6.jar:1.5.6]
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1842) [javax.mail-1.5.6.jar:1.5.6]
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1258) [javax.mail-1.5.6.jar:1.5.6]
Workaround - I am suspecting that we need to increase the timeout. But i want to know why its timeout exactly at 50000.
Please help me on this.
Regards,
Andrews
Hi Prasad, did you find a resolution to this?
My understanding is that the log you are looking at in is for the inbound email processing and that has a default timeout of 50000 milliseconds (50 seconds). The screenshot in Dipesh's reply is for outbound email configuration so i don't think it would affect this.
We also have the same issue here and I think there may have been one or two cases when it caused tickets not to get logged because it timed out halfway through pulling them. I think 50 seconds is a long enough time to connect
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.