[
https://issues.apache.org/jira/browse/SQOOP-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587980#comment-13587980
]
Hudson commented on SQOOP-856:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop200 #572 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/572/])
SQOOP-856: PGBulkLoadExportMapper has an infinite waitFor without any
logging in the event of Interrupted exceptions (Revision
4aa174abee0fc2b8bfb407a4fc5829e22b746413)
Result = SUCCESS
jarcec :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=4aa174abee0fc2b8bfb407a4fc5829e22b746413
Files :
* src/java/org/apache/sqoop/mapreduce/PGBulkloadExportMapper.java
> PGBulkLoadExportMapper has an infinite waitFor without any logging in the
> event of Interrupted exceptions
> ---------------------------------------------------------------------------------------------------------
>
> Key: SQOOP-856
> URL: https://issues.apache.org/jira/browse/SQOOP-856
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.3
> Environment: All, Postgresql database
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Priority: Minor
> Fix For: 1.4.4
>
> Attachments: SQOOP-856.patch
>
>
> The PGBulkloadExportMapper has the following code fragment
> try {
> ...
> process.waitFor();
> ...
> } catch (InterruptedException ie) {
> // interrupted; loop around.
> continue;
> }
> We need to log an exception to note the fact that the thread was interrupted
> ( not sure of any condition except for spurious interrupts)
> Also we need to add a finally block to reset the interrupted condition as
> mentioned in http://bugs.sun.com/view_bug.do?bug_id=6420270
--
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
