How does JTS handle e-mail exceptions ( e.g. connection refused ) ?
We handover email host responsibilities to a "corporate wide" relay. Sometimes JTS reports
2015-10-23 08:57:48,077 [WebContainer : 4 @@ 16:09 <unauthenticated> <Initial Page Load@2b5f8fc8-9f6a-4b12-a733-
b6de24c3aea9> /jts/auth/authrequired] ERROR com.ibm.team.jfs - CRJZS5074E Une
xpected exception sending mail
javax.mail.MessagingException: Could not connect to SMTP host: relay, port: 25;
nested exception is:
java.net.ConnectException: A remote host refused an attempted connect operation.
Does JTS queue the email in some fashion and only removes the need to send after an apparent successful transfer to the mail relay, or does it simply move on to the next task ?
2015-10-23 08:57:48,077 [WebContainer : 4 @@ 16:09 <unauthenticated> <Initial Page Load@2b5f8fc8-9f6a-4b12-a733-
b6de24c3aea9> /jts/auth/authrequired] ERROR com.ibm.team.jfs - CRJZS5074E Une
xpected exception sending mail
javax.mail.MessagingException: Could not connect to SMTP host: relay, port: 25;
nested exception is:
java.net.ConnectException: A remote host refused an attempted connect operation.
Does JTS queue the email in some fashion and only removes the need to send after an apparent successful transfer to the mail relay, or does it simply move on to the next task ?