Topic
  • 5 replies
  • Latest Post - ‏2018-11-17T05:21:21Z by Ananda_Thimmappa
Ananda_Thimmappa
Ananda_Thimmappa
5 Posts

Pinned topic Re: EMAIL alerts not working with 2.1

‏2018-11-16T13:52:47Z | data manger setting sever smtp

Hi, 

 

I am new to data server manager and newly implemented to monitor QA and prod server. 

 

Everything is fine except mail alerts. 

 

I am getting below error message while sending test mail from email server ( product setup). 

 

DS_System (590778) Nov 16, 2018 8:21:36 AM ERROR    Email Controller-Error in EmailService.sendMessage()
The test e-mail could not be sent.
at com.ibm.datatools.config.web.email.EmailController.sendTestEmailMessage(EmailController.java:494)
at com.ibm.datatools.config.web.email.EmailController.handleRequest(EmailController.java:199)
at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:50)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1255)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:743)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:440)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:143)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89)
at dsweb.filter.URLAccessServletFilter.handleURLAccess(URLAccessServletFilter.java:271)
at dsweb.filter.URLAccessServletFilter.doFilter(URLAccessServletFilter.java:103)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:201)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:86)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:995)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1124)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1004)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:76)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:921)
at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:281)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:960)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.wrapHandlerAndExecute(HttpDispatcherLink.java:362)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.ready(HttpDispatcherLink.java:321)
at com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:499)
at com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleNewRequest(HttpInboundLink.java:433)
at com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.processRequest(HttpInboundLink.java:313)
at com.ibm.ws.http.channel.internal.inbound.HttpICLReadCallback.complete(HttpICLReadCallback.java:70)
at com.ibm.ws.channel.ssl.internal.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1763)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(WorkQueueManager.java:503)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQueueManager.java:573)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQueueManager.java:928)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQueueManager.java:1017)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:785)
Caused by: com.ibm.datatools.services.email.exception.EMailServiceException: EML37403E:
 The notification was not sent.
 
 Review the reason, take corrective action if possible, and try again.
 
 javax.mail.MessagingException: Could not connect to SMTP host: smtp.outlook365.com, port: 587;
  nested exception is:
java.net.ConnectException: A remote host did not respond within the timeout period. (Connection timed out)
at com.ibm.datatools.services.email.core.impl.EMailServiceImpl.sendMessage(EMailServiceImpl.java:480)
at com.ibm.datatools.config.web.email.EmailController.sendTestEmailMessage(EmailController.java:490)
... 39 more
Caused by: java.lang.RuntimeException: javax.mail.MessagingException: Could not connect to SMTP host: smtp.outlook365.com, port: 587;
  nested exception is:
java.net.ConnectException: A remote host did not respond within the timeout period. (Connection timed out)
at com.ibm.datatools.services.email.core.impl.EMailServiceImpl.sendTLSMessage(EMailServiceImpl.java:691)
at com.ibm.datatools.services.email.core.impl.EMailServiceImpl.sendMessage(EMailServiceImpl.java:466)
... 40 more
Caused by: javax.mail.MessagingException: Could not connect to SMTP host: smtp.outlook365.com, port: 587;
  nested exception is:
java.net.ConnectException: A remote host did not respond within the timeout period. (Connection timed out)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1282)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370)
at javax.mail.Service.connect(Service.java:297)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at com.ibm.datatools.services.email.core.impl.EMailServiceImpl.sendTLSMessage(EMailServiceImpl.java:687)
... 41 more
Caused by: java.net.ConnectException: A remote host did not respond within the timeout period. (Connection timed out)
at java.net.Socket.connect(Socket.java:666)
at java.net.Socket.connect(Socket.java:606)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:232)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:189)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1250)
... 48 more

 

 

Thanks and Regards,

Ananda T 

  • Ananda_Thimmappa
    Ananda_Thimmappa
    5 Posts

    Re: EMAIL alerts not working with 2.1

    ‏2018-11-16T13:53:55Z  

    We are planning to implement this to monitor production server very soon, so please help me in this to overcome this issue as soon as possible

  • Luke Numrych
    Luke Numrych
    82 Posts

    Re: EMAIL alerts not working with 2.1

    ‏2018-11-16T17:28:11Z  

    The following part of the error message explains what's wrong:
     

     javax.mail.MessagingException: Could not connect to SMTP host: smtp.outlook365.com, port: 587;
      nested exception is:
    java.net.ConnectException: A remote host did not respond within the timeout period. (Connection timed out)

    DSM is telling you that it was trying to connect to the SMTP gateway at smtp.outlook365.com:587, but got no response.  You should validate *outside* of DSM, using network diagnostic tools available in your OS that from the machine on which DSM is installed you have connectivity to the SMTP gateway.  And I am not talking about ping only, as that will not verify that you can connect to port 587 on smtp.outlook365.com.  Even if you verify that, you may be behind a firewall that stops SMTP, regardless of whether you can connect to that port or not.  Work with your network/security admin...

     

    Oh, and you are in the wrong forum.  This forum is for IBM Data Studio, not for IBM Data Server Manager.

    Updated on 2018-11-16T17:34:37Z at 2018-11-16T17:34:37Z by Luke Numrych
  • Ananda_Thimmappa
    Ananda_Thimmappa
    5 Posts

    Re: EMAIL alerts not working with 2.1

    ‏2018-11-16T17:42:21Z  

    The following part of the error message explains what's wrong:
     

     javax.mail.MessagingException: Could not connect to SMTP host: smtp.outlook365.com, port: 587;
      nested exception is:
    java.net.ConnectException: A remote host did not respond within the timeout period. (Connection timed out)

    DSM is telling you that it was trying to connect to the SMTP gateway at smtp.outlook365.com:587, but got no response.  You should validate *outside* of DSM, using network diagnostic tools available in your OS that from the machine on which DSM is installed you have connectivity to the SMTP gateway.  And I am not talking about ping only, as that will not verify that you can connect to port 587 on smtp.outlook365.com.  Even if you verify that, you may be behind a firewall that stops SMTP, regardless of whether you can connect to that port or not.  Work with your network/security admin...

     

    Oh, and you are in the wrong forum.  This forum is for IBM Data Studio, not for IBM Data Server Manager.

    Hi Luke Numrych

     

    Thanks for response, 

     

    I ran script in DSM installed db2 server to verify that whether mail will be trigger from this server.  I received a mail from this server to outlook. 

     

     

    Thanks and Regards,

    Ananda T 

     

     

     

  • Luke Numrych
    Luke Numrych
    82 Posts

    Re: EMAIL alerts not working with 2.1

    ‏2018-11-16T18:25:27Z  

    Hi Luke Numrych

     

    Thanks for response, 

     

    I ran script in DSM installed db2 server to verify that whether mail will be trigger from this server.  I received a mail from this server to outlook. 

     

     

    Thanks and Regards,

    Ananda T 

     

     

     

    I am not sure to what script you are referring, what does it do, or where does it connect to.  To my knowledge DSM does not provide a script to test SMTP connectivity.

  • Ananda_Thimmappa
    Ananda_Thimmappa
    5 Posts

    Re: EMAIL alerts not working with 2.1

    ‏2018-11-17T05:21:21Z  

    Hi Luke, 

     

    Thank you, Its working now. 

     

    Thanks and Regards,

    Ananda T