Skip to content

SPR-9275 Cache Abstraction Exception Handling #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

billkoch
Copy link

@billkoch billkoch commented Sep 7, 2012

Introduced FailSafeCache.

FailSafeCache is intended to wrap existing cache implementations and
gracefully handle any Exceptions thrown by the native cache. The
AbstractCacheManager is responsible for wrapping the native cache(s) IF
the gracefullyHandleExceptions property is true. Otherwise, the
behavior of the AbstractCacheManager remains unchanged.

Issue: SPR-9275

I have signed and agree to the terms of the SpringSource Individual Contributor License Agreement.

native cache implementation.

FailSafeCache is intended to wrap existing cache implementations and
gracefully handle any Exceptions thrown by the native cache.  The
AbstractCacheManager is responsible for wrapping the native cache(s) IF
the gracefullyHandleExceptions property is *true*.  Otherwise, the
behavior of the AbstractCacheManager remains unchanged.

Issue: SPR-9275
@snicoll
Copy link
Member

snicoll commented Jul 1, 2016

Wow, I wasn't even aware of that PR. You're probably aware that SPR-9275 has been implemented in 4.1 in a slightly different approach. Thanks for the PR anyway!

@snicoll snicoll closed this Jul 1, 2016
rstoyanchev added a commit that referenced this pull request Jul 18, 2017
Since there is no reason for an exchange to ever complete without a
ClientResponse I've added a switchIfEmpty check at the WebClient level.

Also, temporarily a second check closer to the problem in the
ReactorClientHttpConnector suggesting a workaround and providing a
reference to the Reactor Netty issue #138.

Issue: SPR-15784
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants