[
https://issues.apache.org/jira/browse/OOZIE-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173845#comment-15173845
]
Harsh J commented on OOZIE-2472:
--------------------------------
I'll try and fix the compile warnings:
{code}
[WARNING]
/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/core/src/test/java/org/apache/oozie/action/email/TestEmailActionExecutor.java:[199,26]
[deprecation] getConf() in Services has been deprecated
[WARNING]
/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/core/src/test/java/org/apache/oozie/action/email/TestEmailActionExecutor.java:[201,26]
[deprecation] getConf() in Services has been deprecated
{code}
But the failing tests seem unrelated:
{code}
Failed tests:
testSamplers(org.apache.oozie.util.TestMetricsInstrumentation):
expected:<4.0> but was:<4.508874329129531>
testForNoDuplicates(org.apache.oozie.event.TestEventGeneration): expected:<3>
but was:<4>
{code}
> 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
>
>
> 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)
