- What is the impact on the customer of the bug?
GLASSFISH-20389 and GLASSFISH-20390, we found this issue. This might be seen
randomly depending upon the order in which "applications" are registered in domain.xml.
- How likely is it that a customer will see the bug and how serious is the bug?
Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)?
What CTS failures are caused by this bug?
This issue will be seen randomly. No CTS failures.
This is a regression compared to GlassFish 2.x, exposed while debugging an issue related to Java EE 7 feature.
- What is the cost/risk of fixing the bug?
Fix is simple, to make sure that the standalone connectors are not stopped before stopping all other applications.
How risky is the fix? How much work is the fix? Is the fix complicated?
Fix is simple.
Fix is reviewed by Hong Zhang (Deployment)
- Is there an impact on documentation or message strings?
- Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
Deployment, Connector, EJB SQE Tests
[I have verified Connector SQE tests]
I have also verified that the following tests pass :
QL (Web, Classic), deployment-dev, ejb-dev, connector-dev, jdbc-dev, connector-standalone-cts (Web, Classic), resources-admin-cli.
- Which is the targeted build of 4.0 for this fix?
- If this an integration of a new version of a component from another project,
what are the changes that are being brought in? This might be list of
Jira issues from that project or a list of revision messages.