[GLASSFISH-18073] Named query validation happens too late Created: 22/Dec/11  Updated: 20/Dec/16  Resolved: 22/Dec/11

Status: Resolved
Project: glassfish
Component/s: entity-persistence
Affects Version/s: 3.1.2_dev, 4.0_dev
Fix Version/s: 3.1.2_dev, 4.0_dev

Type: Bug Priority: Major
Reporter: Mitesh Meswani Assignee: Mitesh Meswani
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_2-approved

 Description   

Currently Named query validation happens at first EM creation. This results in two issues.
1. Archives with invalid named queries are deployed successfully and we get a runtime exception while using them
2. If Java2db is turned on, the exception for named query validation gets the container into an inconsistent state.

This issue has been reported in various user forums and we have also observed Arun struggling with it while developing JavaOne demo.



 Comments   
Comment by Mitesh Meswani [ 22/Dec/11 ]
  • What is the impact on the customer of the bug?
    Considerable. When the container gets into inconsistent state, there is not indication of why it happened. The only workaround is to restart the appserver.
  • How likely is it that a customer will see the bug and how serious is the bug?
    Very likely.

Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)?
Yes. from 2.x

  • What is the cost/risk of fixing the bug?
    The fix is already implemented and tested in local workspace.
  • How risky is the fix? How much work is the fix? Is the fix complicated?
    Low risk. I have already tested deployment with various packaging scenarios to ensure that there is no regression
  • Is there an impact on documentation or message strings?
    No.
  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
    Standard persistence test suite against any database.
  • Which is the targeted build of 3.1.2 for this fix?
    Next one.
Comment by Mitesh Meswani [ 22/Dec/11 ]

Persistence related changes committed as rev 51719 in 3.1.2 branch and rev 51720 in trunk

Generated at Thu Apr 27 09:27:21 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.