[jboss-jira] [JBoss JIRA] (WFCORE-210) IO error during deployment scanning triggers undeployment
RH Bugzilla Integration (JIRA)
issues at jboss.org
Tue Nov 25 03:28:45 EST 2014
[ https://issues.jboss.org/browse/WFCORE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022547#comment-13022547 ]
RH Bugzilla Integration commented on WFCORE-210:
------------------------------------------------
Vladimir Dosoudil <dosoudil at redhat.com> changed the Status of [bug 1159709|https://bugzilla.redhat.com/show_bug.cgi?id=1159709] from MODIFIED to ON_QA
> IO error during deployment scanning triggers undeployment
> ---------------------------------------------------------
>
> Key: WFCORE-210
> URL: https://issues.jboss.org/browse/WFCORE-210
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha10
> Reporter: James Livingston
> Assignee: Emmanuel Hugonnet
> Fix For: 1.0.0.Alpha14
>
>
> If an IO error such as reaching the file descriptor limit occurs during deployment scanning, the scanner continues with an empty deployment list causing it to undeploy applications.
> This occurs because FileSystemDeploymentService.scanDirectory() treats File.listFiles() returning null as an empty list rather than an error. http://docs.oracle.com/javase/7/docs/api/java/io/File.html#listFiles%28%29 notes that it returns an empty array if the directory is empty, and null if it is not a directory or an IO error occurs.
> It should instead respond to a null return value by aborting the scanner run, with a log message, and not proceed to undeploy applications.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
More information about the jboss-jira
mailing list