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.

Sign up for GitHub

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

Jump to bottom

Avoid endless Invalid Bundle exceptions in log #228

Closed
rymsha opened this issue Dec 30, 2024 · 0 comments · Fixed by #231
Closed

Avoid endless Invalid Bundle exceptions in log #228

rymsha opened this issue Dec 30, 2024 · 0 comments · Fixed by #231
Assignees
@rymsha
Labels
bug Something isn't working

Comments

@rymsha
Copy link
Contributor

rymsha commented Dec 30, 2024 •
edited
Loading

When application is stopped all scheduled tasks should be stopped, but it is not guaranteed as it is developer's responsibility to unschedule in dispose.

Instead use OSGi Service that is has better guarantees to stop SheduledThreadPool at least till enonic/xp#10844 is fixed
@rymsha rymsha added the enhancement New feature or request label Dec 30, 2024
@rymsha rymsha self-assigned this Dec 30, 2024
@rymsha rymsha linked a pull request Jan 7, 2025 that will close this issue
#228 verify bundle context to avoid endless exceptions in log #231
Merged
@rymsha rymsha changed the title Verify bundle context to avoid endless exceptions in log Avoid endless Invalid Bundle exceptions in log Jan 7, 2025
rymsha added a commit that referenced this issue Jan 7, 2025
@rymsha
#228 verify bundle context to avoid endless exceptions in log (#231)
66de7d2
@rymsha rymsha added bug Something isn't working and removed enhancement New feature or request labels Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rymsha rymsha

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#228 verify bundle context to avoid endless exceptions in log enonic/lib-cron
1 participant
@rymsha