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

Timer should not be a singleton #1047

Closed
Ladicek opened this issue Sep 18, 2024 · 0 comments · Fixed by #1048
Closed

Timer should not be a singleton #1047

Ladicek opened this issue Sep 18, 2024 · 0 comments · Fixed by #1048
Assignees
Milestone

Comments

@Ladicek
Copy link
Contributor

Ladicek commented Sep 18, 2024

In WildFly, if there are multiple deployments using SmallRye Fault Tolerance, multiple timers are created. This used to work fine, but fails now. We need to rollback the singleton nature of ThreadTimer, while preserving metrics. The only possible way I can think of is adding a tag (or attribute) to the ft.timer.scheduled metric identifying the timer.

@Ladicek Ladicek self-assigned this Sep 18, 2024
@Ladicek Ladicek added this to the 6.4.1 milestone Sep 20, 2024
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 a pull request may close this issue.

1 participant