Bug 802793 - Content Deployment Files Name Clashes - JBoss AS5 Plugin
Summary: Content Deployment Files Name Clashes - JBoss AS5 Plugin
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.4.0
Assignee: Stefan Negrea
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 758753
TreeView+ depends on / blocked
 
Reported: 2012-03-13 14:15 UTC by Stefan Negrea
Modified: 2013-09-01 10:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-01 10:01:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Stefan Negrea 2012-03-13 14:15:51 UTC
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:
Everytime

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 10:01:04 UTC
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.