You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Ivan Mitic (JIRA)" <ji...@apache.org> on 2012/06/27 04:14:44 UTC
[jira] [Created] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Ivan Mitic created HADOOP-8534:
----------------------------------
Summary: TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Key: HADOOP-8534
URL: https://issues.apache.org/jira/browse/HADOOP-8534
Project: Hadoop Common
Issue Type: Bug
Components: conf
Affects Versions: 1.0.0
Reporter: Ivan Mitic
Java xml parser keeps file locked after SAXException, causing the following tests to fail:
- TestQueueManagerForJobKillAndJobPriority
- TestQueueManagerForJobKillAndNonDefaultQueue
{{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
Forum references on the problem and the fix:
http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Ivan Mitic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402759#comment-13402759 ]
Ivan Mitic commented on HADOOP-8534:
------------------------------------
Thanks Bikas and Chuan!
bq. Looks like the same fix was made for instance of String.
Right, I noticed that the above piece of code for {{URL}} had the same problem, so I fixed it. Re-run the commit & problematic tests to make sure the updated fix works fine.
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Chuan Liu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402738#comment-13402738 ]
Chuan Liu commented on HADOOP-8534:
-----------------------------------
+1 Change looks good to me.
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Ivan Mitic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Mitic updated HADOOP-8534:
-------------------------------
Attachment: HADOOP-8534-branch-1-win_Parser(2).patch
I see, thanks! Attaching updated patch that addresses the comment.
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Bikas Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401903#comment-13401903 ]
Bikas Saha commented on HADOOP-8534:
------------------------------------
+1. Would wrapping it in a BufferedInputStream help?
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Bikas Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402481#comment-13402481 ]
Bikas Saha commented on HADOOP-8534:
------------------------------------
I was just saying that the code doing the same thing in other places uses BufferedStreams. So there is a precedent for using it.
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Ivan Mitic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402417#comment-13402417 ]
Ivan Mitic commented on HADOOP-8534:
------------------------------------
bq. Isnt it reading from a URL that could potentially be remote? I see that BufferedInputStream is used for the File input immediately following the URL input.
Sorry, I am not following you, do you mind clarifying? In this case we are getting a resource from the classpath (for example {{hdfs-site.xml}}).
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Ivan Mitic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Mitic updated HADOOP-8534:
-------------------------------
Attachment: HADOOP-8534-branch-1-win_Parser.patch
Attaching a patch with the fix.
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Ivan Mitic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Mitic reassigned HADOOP-8534:
----------------------------------
Assignee: Ivan Mitic
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8534) Some tests leave a config file open
causing failure on windows
Posted by "Sanjay Radia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjay Radia resolved HADOOP-8534.
----------------------------------
Resolution: Fixed
Committed to Hadoop-1 windows branch. Thanks Ivan.
> Some tests leave a config file open causing failure on windows
> --------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Bikas Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402399#comment-13402399 ]
Bikas Saha commented on HADOOP-8534:
------------------------------------
Isnt it reading from a URL that could potentially be remote? I see that BufferedInputStream is used for the File input immediately following the URL input.
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Bikas Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402753#comment-13402753 ]
Bikas Saha commented on HADOOP-8534:
------------------------------------
Looks like the same fix was made for instance of String.
+1
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8534)
TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
Posted by "Ivan Mitic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401909#comment-13401909 ]
Ivan Mitic commented on HADOOP-8534:
------------------------------------
Thanks for reviewing Bikas!
bq. Would wrapping it in a BufferedInputStream help?
I assume you mean from the performance standpoint. I don't think there is a need for that given the scenario.
> TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8534) Some tests leave a config file open
causing failure on windows
Posted by "Sanjay Radia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjay Radia updated HADOOP-8534:
---------------------------------
Summary: Some tests leave a config file open causing failure on windows (was: TestQueueManagerForJobKillAndJobPriority and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows)
> Some tests leave a config file open causing failure on windows
> --------------------------------------------------------------
>
> Key: HADOOP-8534
> URL: https://issues.apache.org/jira/browse/HADOOP-8534
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch
>
>
> Java xml parser keeps file locked after SAXException, causing the following tests to fail:
> - TestQueueManagerForJobKillAndJobPriority
> - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira