[
https://issues.apache.org/jira/browse/OOZIE-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174180#comment-15174180
]
Robert Kanter commented on OOZIE-2472:
--------------------------------------
A few things:
- Instead of putting the default value of 10000ms in the code, let's put it in
oozie-default.xml
- Instead of https://goo.gl/uAz4jp we should either use the long url or a short
url from https://s.apache.org
- When we catch the {{Exception}} in the {{testServerTimeouts}} test, is there
some way to verify that it was due to a socket timeout and not some other
problem? (i.e. check the {{Exception}} type or part of the message)
> Remove infinite socket timeouts in the Oozie email action
> ---------------------------------------------------------
>
> Key: OOZIE-2472
> URL: https://issues.apache.org/jira/browse/OOZIE-2472
> Project: Oozie
> Issue Type: Bug
> Components: action
> Affects Versions: 4.2.0
> Reporter: Harsh J
> Assignee: Harsh J
> Attachments: OOZIE-2472.patch, OOZIE-2472.patch, OOZIE-2472.patch
>
>
> We're missing explicit socket timeout configs in EmailActionExecutor, and it
> appears that the default timeouts are all infinite by default:
> https://goo.gl/uAz4jp
> If the email server goes unresponsive in a certain ways, the email action
> executor would pile up on the executor threads, waiting on the SMTP host.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
