
| Key: |
BATCH-682
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Dave Syer
|
| Reporter: |
Dave Syer
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
0.5d
|
|
|
Remaining Estimate:
|
0.5d
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
|
Use SoftReference and/or expiry to store entries in RetryContextCache implementation(s). If the map-based cache is used in a multi-VM environment, stale cache entries can easily be accumulated inadvertently because the successful processing of a previously failed item happened on a different node than the original failure. A good start would be to use SoftReferences in the map-based implementation. Expiry and more complicated features would be best left to mature cache technologies, and custom implementations of the RetryContextCache interface.
|
|
Description
|
Use SoftReference and/or expiry to store entries in RetryContextCache implementation(s). If the map-based cache is used in a multi-VM environment, stale cache entries can easily be accumulated inadvertently because the successful processing of a previously failed item happened on a different node than the original failure. A good start would be to use SoftReferences in the map-based implementation. Expiry and more complicated features would be best left to mature cache technologies, and custom implementations of the RetryContextCache interface. |
Show » |
|