[MGNLIMG-51] Concurrency: locking ImageGenerationJobs for same node Created: 26/May/09  Updated: 04/Dec/13  Resolved: 29/Jun/09

Status: Closed
Project: Imaging
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.1

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLETK-6 Potential concurrency bug in imaging Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

See TODOs in info.magnolia.imaging.caching.ImageGenerationJob. This object is used as a key in the computing map of CachingImageStreamer. It's assuming that the parameter of the job (as provided by ParameterProvider) has a correct implementation of equals()/hashCode(). This is not the case for DefaultContent.

Possible solutions:

  • Make this compare the ParameterProvider instances instead of the parameter itself, so that ContentParameterProvider.equals() would compare, for instance, the uuid of its parameter.
  • Wrap the nodes into a wrapper whose equals/hashCode methods use the uuid or other attribute for comparison

Generated at Mon Feb 12 02:11:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.