Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1159709

Summary: IO error during deployment scanning triggers undeployment
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Livingston <jlivings>
Component: Domain ManagementAssignee: Emmanuel Hugonnet (ehsavoie) <ehugonne>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.1CC: brian.stansberry, dandread, joallen, kkhan
Target Milestone: DR11   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP 6, `FileSystemDeploymentService.scanDirectory()` method treated the null return value of `File.listFiles()` as an empty list rather than an error. As a result, IO errors occurring during deployment scanning could trigger the un-deployment of applications. This issue has been addressed and in this release of the product, deployed applications are no longer undeployed if file limit is reached.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Livingston 2014-11-03 05:12:48 UTC 
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.
Comment 3 Petr Kremensky 2014-12-02 08:20:20 UTC 
Verified on EAP 6.4.0.DR11

Deployed applications are no longer undeployed if file limit is reached.