How bad is its impact? (Severity)
Identify why the fix needs to occur now:
- Is a regression of functionality or performance available in a prior release
- An in-your-face issue that will touch the majority of users
How often does it happen? (Frequency)
- We expose jdbc, jms resources as OSGi service references and when the underlying resource is deleted in GlassFish, they are not removed from OSGi service references. So, any OSGi bundle that uses these service references will face stale resource issue.
How much effort is required to fix it? (Cost)
- Minor, made sure that only one instance of resource-manager per type (jdbc, jms) is available at runtime.
What is the risk of fixing it? (Risk)
- Very minimal, fix is localized to OSGi-ee-resources module (does not affect GlassFish's core container modules)
- Will make sure that QL (Web, Classic), connector-dev, jdbc-dev, connector-standalone-cts (Web, Classic), resources-admin-cli, connector-sqe-tests pass.
Does a work around for the issue exist? Can the workaround be reasonably employed by the end user?
If the issue is not fixed should the issue and its workaround (if applicable) be described in the Release Notes?
How long has the bug existed in the product?
- 3-4 months (a regression).
Do regression tests exist for this issue?
- Yes, will be adding a new test-case for this use-case.
Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
When will a tested fix be ready for integration?