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

Timing issue in StartupOrderResolver #1244

Closed
Niranjan-K opened this issue Jan 2, 2017 · 0 comments
Closed

Timing issue in StartupOrderResolver #1244

Niranjan-K opened this issue Jan 2, 2017 · 0 comments
Assignees
Labels
Milestone

Comments

@Niranjan-K
Copy link
Contributor

[Moved from [carbon-kernel jira(https://wso2.org/jira/browse/CARBON-15998)]

It seems there is a race condition in,

  1. OSGi framework notifying a component on a dependency (@reference()) and
  2. StartupOrderResolver notifying a component when all capabilities are ready
    So, a component sometimes notified via the "onAllRequiredCapabilitiesAvailable" before it actually get notified via OSGi framework about the service availability
@Niranjan-K Niranjan-K modified the milestones: 5.2.0-alpha, 5.2.0-m4 Jan 2, 2017
@Niranjan-K Niranjan-K self-assigned this Jan 9, 2017
jsdjayanga added a commit to jsdjayanga/carbon-kernel that referenced this issue Mar 13, 2017
jsdjayanga added a commit to jsdjayanga/carbon-kernel that referenced this issue Mar 14, 2017
jsdjayanga added a commit to jsdjayanga/carbon-kernel that referenced this issue Mar 15, 2017
senthuran16 pushed a commit to senthuran16/carbon-kernel that referenced this issue Aug 29, 2023
[UMT] Support legacy browsers that misinterpret SameSite=None cookie property.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants