Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.0.0.BETA
-
Fix Version/s: EE-3.0.0.GA
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces
Description
If dynamic resource names are not unique and collisions occur across server restarts, the behavior can be unpredictable.
Issue Links
- blocks
-
ICE-7685
ace:dataExporter sometimes fails in ACE Showcase when running as a portlet
-
- Closed
-
Activity
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #28383 | Fri Mar 16 15:29:55 MDT 2012 | ted.goddard | use UUID for dynamic resource names ( |
| Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/core/src/main/java/org/icefaces/application/ResourceRegistry.java
|
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #28384 | Fri Mar 16 15:31:38 MDT 2012 | ted.goddard | use UUID for dynamic resource names ( |
| Files Changed | ||||
|
MODIFY
/icefaces3/branches/icefaces-3.0.x-maintenance/icefaces/core/src/main/java/org/icefaces/application/ResourceRegistry.java
|
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Ted Goddard [ ted.goddard ] |
The fix is to use a random UUID for all resource names not assigned by the application. In general, it is not recommended that the application assign a resource name unless there is a specific reason to do so.
Show
Ted Goddard
added a comment - The fix is to use a random UUID for all resource names not assigned by the application. In general, it is not recommended that the application assign a resource name unless there is a specific reason to do so.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
The current resource naming scheme made use of a scope prefix followed by an integer incremented for each resource created. This was unique for each time the server is started, but collisions could occur if the server is restarted and sessions are brought back from a serialized form. Potentially, collisions could also occur in a cluster, since different indexes would be used but user sessions would be replicated across the cluster.