Skip to content
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

Actuator endpoint time-to-live caching is not respected on WebFlux #18339

Closed
wants to merge 2 commits into from

Conversation

dreis2211
Copy link
Contributor

Hi,

this PR is an attempt to fix #18324 . I'm not super familiar with the reactive side of things, but the proposed solution seems to fix the provided sample in #18324. A proper review and feedback is therefore highly appreciated.

Let me know what you think.
Cheers,
Christoph

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 24, 2019
@dreis2211
Copy link
Contributor Author

Test failure seems unrelated

@philwebb philwebb added type: bug A general bug and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 24, 2019
@philwebb philwebb added this to the 2.1.x milestone Sep 24, 2019
@philwebb philwebb changed the title Handle Mono responses in CachingOperationInvoker Actuator endpoint time-to-live caching is not respected on WebFlux Sep 24, 2019
philwebb pushed a commit that referenced this pull request Sep 29, 2019
Update `CachingOperationInvoker` so that TTL caching is applied directly
to reactive types. Prior to this commit, a `Mono` would be cached, but
the values that it emitted would not.

See gh-18339
philwebb added a commit that referenced this pull request Sep 29, 2019
Extract reactor specific code to an inner class to protect
against ClassNotFound exceptions if reactor is not in use.

Also add support for `Flux`.

See gh-18339
@philwebb philwebb closed this in a1fb1bc Sep 29, 2019
@philwebb
Copy link
Member

Thanks @dreis2211, this is now merged to 2.1.x and 2.2.x. I changing things slightly because I realized that we need to guard against reactor not being on the classpath. I also added Flux support whilst I was at it. Thanks again!

@philwebb philwebb modified the milestones: 2.1.x, 2.1.9 Sep 29, 2019
@snicoll

This comment has been minimized.

@philwebb

This comment has been minimized.

@snicoll

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TTL property is not working for health indicator when using webflux
4 participants