[
https://issues.apache.org/jira/browse/OOZIE-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444382#comment-13444382
]
Alejandro Abdelnur commented on OOZIE-977:
------------------------------------------
harsh, the timeout should be an oozie server config property, not a job
property. It is the administration who decides/sets the timeout. default in
oozie-default.xml should be 15 or 30 secs. makes sense?
> NotificationXCommand (job.notification queue entry) should set a timeout in
> the HTTP connections it makes
> ---------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-977
> URL: https://issues.apache.org/jira/browse/OOZIE-977
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.1.3
> Reporter: Harsh J
> Assignee: Harsh J
> Attachments: OOZIE-977.patch, OOZIE-977.patch
>
>
> Right now, the NotificationXCommand, which makes a HTTP connection to the
> oozie.wf.workflow.notification.url provided WF url, does not set a timeout.
> The default timeout of HttpURLConnection is infinite, and hence this can
> easily cause a blockage on the queued commands if the URL is external and the
> connections are stuck on it for long times / forever.
> We should make this connection with a fixed timeout value. There is a retry
> factor anyway, so that should cause no harm. The timeout value can be
> configurable at the Oozie server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
