[
https://issues.apache.org/jira/browse/OOZIE-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445467#comment-13445467
]
Hadoop QA commented on OOZIE-977:
---------------------------------
Testing JIRA OOZIE-977
Cleaning local svn workspace
{code}
----------------------------
+1 PATCH_APPLIES
CLEAN cleaned target directories
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch does adds/modifies 3 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 904
Tests failures: 0
Tests errors: 0
+1 DISTRO
+1 distro tarball builds with the patch
----------------------------
{code}
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/74/
> 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: Alejandro Abdelnur
> Attachments: OOZIE-977.patch, OOZIE-977.patch, 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
