When you start the workflow, in the last step, emails are sent using SMTP. When executing a task, the process throws the error java.net.SocketTimeoutException: Read timed out
I suspect this is due to the fact that too little time is allotted for the connection, which is why the SMTP server does not have time to return a response. Is there a configuration file somewhere in ONE desktop where you can manually set the time on timeout ?
Best answer by Rob Coops
Hi FCB Developer,
Looking at the documentation for the package used: https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html it indicates that the default timeout is set to infinite. Since there is no overwrite from Ataccama as you can see here: https://support.ataccama.com/home/display/AOP/JVM+Configuration the default infinite timeout will be there.
Now the actual timeout happens much lower down on the java socket level it self, which is by default 2 minutes. Since this is a read timeout when attempting to send a message, I would venture a guess and say that you are likely looking at a connectivity problem where the socket gets opened to the remote host (your SMTP server in this case) but no information is received.
A good way to confirm that all if right is to attempt to make a connection to the SMTP server from the host where the workflow is executed. Using a command like: nc -v -u smtp.server.hostname smpt_server_port_number to confirm that you can connect to the SMTP server and that things work correctly.
+1Hi FCB Developer,
Looking at the documentation for the package used: https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html it indicates that the default timeout is set to infinite. Since there is no overwrite from Ataccama as you can see here: https://support.ataccama.com/home/display/AOP/JVM+Configuration the default infinite timeout will be there.
Now the actual timeout happens much lower down on the java socket level it self, which is by default 2 minutes. Since this is a read timeout when attempting to send a message, I would venture a guess and say that you are likely looking at a connectivity problem where the socket gets opened to the remote host (your SMTP server in this case) but no information is received.
A good way to confirm that all if right is to attempt to make a connection to the SMTP server from the host where the workflow is executed. Using a command like: nc -v -u smtp.server.hostname smpt_server_port_number to confirm that you can connect to the SMTP server and that things work correctly.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
