DX On-Prem Error transmitting Email via mail.ca.com
search cancel

DX On-Prem Error transmitting Email via mail.ca.com

book

Article ID: 232769

calendar_today

Updated On:

Products

DX Application Performance Management

Issue/Introduction

Attempting to use DX APM On-Prem release 21.3.1 password reset function in DX Platform browser UI.
No error is reported in browser UI.
dxi-readserver log reports the below Exception:

 [AsynchSendRequest,pool-34-thread-7] ERROR [] - TID[0|154750585|154750585|dxi-adminui-6b4d67f77c-:2:8120] 2751108: Error while transmitting Email to recipient(s) [email protected]: Mail server connection failed; nested exception is com.sun.mail.util.MailConnectException: Couldn't connect to host, port: mail.ca.com, 25; timeout 1000;
  nested exception is:
 java.net.UnknownHostException: mail.ca.com. Failed messages: com.sun.mail.util.MailConnectException: Couldn't connect to host, port: mail.ca.com, 25; timeout 1000;
  nested exception is:
 java.net.UnknownHostException: mail.ca.com
com.ca.emm.corejsvr.ExceptionWithNC: 2751108: Error while transmitting Email to recipient(s) [email protected]: Mail server connection failed; nested exception is com.sun.mail.util.MailConnectException: Couldn't connect to host, port: mail.ca.com, 25; timeout 1000;
  nested exception is:
 java.net.UnknownHostException: mail.ca.com. Failed messages: com.sun.mail.util.MailConnectException: Couldn't connect to host, port: mail.ca.com, 25; timeout 1000;
  nested exception is:
 java.net.UnknownHostException: mail.ca.com
 at com.ca.emm.notify.engine.provider.SMTPProviderService$AsynchSendRequest.call(SMTPProviderService.java:453) [notify-engine-2.0.1.37.jar:?]
 at com.ca.emm.notify.engine.provider.SMTPProviderService$AsynchSendRequest.call(SMTPProviderService.java:386) [notify-engine-2.0.1.37.jar:?]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_302]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_302]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_302]
 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_302]
Caused by: org.springframework.mail.MailSendException: Mail server connection failed; nested exception is com.sun.mail.util.MailConnectException: Couldn't connect to host, port: mail.ca.com, 25; timeout 1000;
  nested exception is:
 java.net.UnknownHostException: mail.ca.com. Failed messages: com.sun.mail.util.MailConnectException: Couldn't connect to host, port: mail.ca.com, 25; timeout 1000;
  nested exception is:
 java.net.UnknownHostException: mail.ca.com
 at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:448) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:361) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:356) ~[spring-context-support-5.3.10.jar:5.3.10]
 at com.ca.emm.notify.engine.provider.SMTPProviderService$AsynchSendRequest.call(SMTPProviderService.java:438) ~[notify-engine-2.0.1.37.jar:?]
 ... 5 more
Caused by: com.sun.mail.util.MailConnectException: Couldn't connect to host, port: mail.ca.com, 25; timeout 1000
 at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2209) ~[javax.mail-1.6.2.jar:1.6.2]
 at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:740) ~[javax.mail-1.6.2.jar:1.6.2]
 at javax.mail.Service.connect(Service.java:366) ~[javax.mail-1.6.2.jar:1.6.2]
 at org.springframework.mail.javamail.JavaMailSenderImpl.connectTransport(JavaMailSenderImpl.java:518) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:437) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:361) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:356) ~[spring-context-support-5.3.10.jar:5.3.10]
 at com.ca.emm.notify.engine.provider.SMTPProviderService$AsynchSendRequest.call(SMTPProviderService.java:438) ~[notify-engine-2.0.1.37.jar:?]
 ... 5 more
Caused by: java.net.UnknownHostException: mail.ca.com
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184) ~[?:1.8.0_302]
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_302]
 at java.net.Socket.connect(Socket.java:607) ~[?:1.8.0_302]
 at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:357) ~[javax.mail-1.6.2.jar:1.6.2]
 at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:238) ~[javax.mail-1.6.2.jar:1.6.2]
 at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2175) ~[javax.mail-1.6.2.jar:1.6.2]
 at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:740) ~[javax.mail-1.6.2.jar:1.6.2]
 at javax.mail.Service.connect(Service.java:366) ~[javax.mail-1.6.2.jar:1.6.2]
 at org.springframework.mail.javamail.JavaMailSenderImpl.connectTransport(JavaMailSenderImpl.java:518) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:437) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:361) ~[spring-context-support-5.3.10.jar:5.3.10]
 at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:356) ~[spring-context-support-5.3.10.jar:5.3.10]
 at com.ca.emm.notify.engine.provider.SMTPProviderService$AsynchSendRequest.call(SMTPProviderService.java:438) ~[notify-engine-2.0.1.37.jar:?]
 ... 5 more

Environment

Release : 21.3

Component : Integration with APM

Resolution

We did configure the mail server yesterday and test prior to submitting the case.

It appears there is some delay before the mail server configuration update is propagated to the service.

 

I tested again this morning and the email is was generated successfully using SSA mail server.

This case may now be closed.