Bug 1159709 – IO error during deployment scanning triggers undeployment

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1159709 - IO error during deployment scanning triggers undeployment

Summary:	IO error during deployment scanning triggers undeployment

Status:	VERIFIED

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Domain Management (Show other bugs)
Sub Component:
Version:	6.3.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR11
Target Release:	EAP 6.4.0
Assigned To:	Emmanuel Hugonnet (ehsavoie)
QA Contact:	Petr Kremensky
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-03 00:12 EST by James Livingston
Modified:	2018-03-06 15:40 EST (History)
CC List:	4 users (show)

See Also:
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:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFCORE-210	Major	Resolved	IO error during deployment scanning triggers undeployment	2018-10-05 09:53 EDT

Groups: None (edit)

Description James Livingston 2014-11-03 00:12:48 EST

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 03:20:20 EST

Verified on EAP 6.4.0.DR11

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

Note You need to log in before you can comment on or make changes to this bug.