Openwings Home
Introduction
Search
In the News
Frequently Asked Questions
Registration
Open Forum
Openwings Tutorial
Bug Database
Openwings API
Download
Expert Teams
Process Management Office
Projects
Links
Terms of Use
Comment on this bug

05305:

Error installing components with identical UniqueIDs

Category: Install
Status: Closed

Severity: HIGH
Reported against release: 0.8
Fixed in release: 0.9

PROBLEM:

1) When using hotinstall on large images (800K), the hotinstall does 
not work very well.  Specifically, I installed the RedBlueTopLink_im 
(built on or after 4/23) using the drag and drop in the Windows 
explorer.  Looking at the log (which is attached), it appears that the 
hotinstall saw the file prior to the file copy completing.  The file 
was not installed; it remained in the hotinstall directory.

2) A second copy of the file yielded a concurrent access exception, 
indicating another problem (in the same log).  This caused the 
component to not be resolved until the core was restarted.

ANALYSIS:

ANALYSIS (Implementation):

The root cause is human error. If a user uses another ICD to create a 
new ICD, the user may forget to ensure the uniqueID is unique.

The suggested solution is to modify the Installer to check the uniqueID 
before jar extraction.

WORKAROUND:

There are several potential workarounds:

1) Don't use hotinstall (not really a workaround)
2) Delete and re-copy the file (it might work the second time, it might 
not ...)
3) Restart the installer or core.

back to top

home | vision | search | in the news | faq | registration | open forum | tutorial | bug database
 API | download | expert teams | process management office | projects | links | terms of use

© Copyright 2001-2006 General Dynamics C4 Systems. All rights reserved.