[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: |
|
||||||||
| 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:
|