-
Notifications
You must be signed in to change notification settings - Fork 470
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
OSGi does not always init properly when adding Workflow Actionlets #30291
Comments
Failed IQA: Still requires a redeployment of the plugin that includes actionlets for them to get installed/added. First time:
After reapplying the plugin:
|
Was this in a cluster and you hit the "reinit plugins"? If so, I think that it is another issue and not the original one. |
… any workflow actionlets
… any workflow actionlets
… any workflow actionlets
…any workflow actionlets (#30531) To avoid possible race condition, the OSGI actionlets registration is now preceded by a check that makes sure (after a reasonable number of tries) that OSGI framework is fully loaded.
…any workflow actionlets (#30531) To avoid possible race condition, the OSGI actionlets registration is now preceded by a check that makes sure (after a reasonable number of tries) that OSGI framework is fully loaded.
Failed IQA: Still not loading actionlets consistently when the plugin is installed. |
I think we are battling two issues. The original PR fixed the issue of an actionlet loading locally. The second issue is with the use of shedlock to reinit osgi in a cluster that prevents multiple nodes from reloading osgi correctly. We should not be using shedlock here I don't think. I would be interested in the original reasoning for doing so. |
…when registergin OSGI plugin with actionlets
Passed IQA: Two starts of the plugin both correctly installing the actionlets:
|
Approved: Tested on trunk_3d77285, Docker, macOS 14.5, FF v126.0.1 |
Parent Issue
No response
Problem Statement
When dotCMS is running with a plugin that provides a workflow action, and dotCMS gets restarted, there is a race condition between OSGi initing and the plugin trying to register the actionlet. If OSGI is fully initied, the actionlet will register. If not, the actionlet will not show up and the plugin needs to be manually re-added to be able to use the actionlet.
Steps to Reproduce
Its hard to reproduce because does not happen all the time.
It especially happens if your felix-cache is persisted across restarts.
Acceptance Criteria
make this not happen
dotCMS Version
24.09
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: