[GLASSFISH-20356] JPA remote SLSB tests failed with CDI enabled Created: 19/Apr/13 Updated: 03/May/13 Resolved: 26/Apr/13
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
JPA remote SLSB tests failed with CDI enabled
Tests failed on b85 promoted, but passed on b84 promoted.
Thanks Mitesh for the initial analysis:
|Comment by Mitesh Meswani [ 19/Apr/13 ]|
Assigning to JJ since this issue is due to enable-implicit-cdi
|Comment by tlcksnyder [ 19/Apr/13 ]|
Exception from 1153 log ftp://adc2120166.us.oracle.com/pub/tmp/appserver-sqe_130418_EJB3_six_test_failure/issue_1153_basic.server.log.txt:
|Comment by jjsnyder83 [ 19/Apr/13 ]|
Can you provide info on how to download and execute the tests?
|Comment by sherryshen [ 19/Apr/13 ]|
1) To set up test env, please reference the instruction section I, IIa
After check out, do
$ ant start-domain
in $SPS_HOME to start glassfish and derby.
2) To run test suite, do "ant all" in test suite dir, e.g.
|Comment by jjsnyder83 [ 25/Apr/13 ]|
What is the impact on the customer of the bug?
How likely is it that a customer will see the bug and how serious is the bug?
What is the cost/risk of fixing the bug?
How risky is the fix? How much work is the fix? Is the fix complicated?
Is there an impact on documentation or message strings?
Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
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,
|Comment by jjsnyder83 [ 26/Apr/13 ]|
Committed revision 61664.
|Comment by sherryshen [ 03/May/13 ]|
Verified the fix on build 87 promoted on May 1, 2013.