Bug 802793 - Content Deployment Files Name Clashes - JBoss AS5 Plugin
Content Deployment Files Name Clashes - JBoss AS5 Plugin
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: RHQ 4.4.0
Assigned To: Stefan Negrea
Mike Foley
Depends On:
Blocks: 758753
  Show dependency treegraph
Reported: 2012-03-13 10:15 EDT by Stefan Negrea
Modified: 2013-09-01 06:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-01 06:01:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stefan Negrea 2012-03-13 10:15:51 EDT
Description of problem:
There could be file name clashes if there are multiple deployments occurring (almost) simultaneously on the same agent. This can happen if an application server has two apps with the same name or if an agent monitors two AS5 servers on the same host (and a deployment is requested). Affected by this are the backups of original applications as well archives of content to be deployed.

How reproducible:

Steps to Reproduce Problem :
1. Inventory two AS5 servers on the same host.
2. Deploy (almost) simultaneously (using CLI) new content for applications with identical names on both servers. The original name of the application should be identical, however the new deployment should be different.
3. Wait for the deployments to complete.
4. Check the files for each deployment.
Actual results:
The files deployed on the two servers are identical. The files from one the deployments has been deployed on both servers.

Expected results:
The files deployment to each server are different.
Comment 1 Heiko W. Rupp 2013-09-01 06:01:04 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.

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