Fix JNDI concurrency issue and other improvements #107
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Protect HashMap from access by 2nd thread until it's fully populated. refine fix to concurrency issue
… caches. Use system bundle context to track more bundles. Extend the cache availbiliy to JNDI calls during bundle start()/stop() methods. The tracker's bundleRemoved is deleted since it will only be called after a bundle transitions from STOPPING->STOPPED at which point the framework has done cleanup and calling ungetService is not needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix concurrency issue in CachingTracker. Made changes to the BundleTracker setup to increase the set of client bundles tracked.