Community
Participate
Working Groups
This bug is not a real bug, it's used to describe intermittent jpa test failures on application servers, it should not be assigned to anybody. 1. org.eclipse.persistence.testing.tests.jpa.relationships.ExpressionJUnitTestSuite.testLocateWithSingleArgument failed with "junit.framework.AssertionFailedError: Test error: IncorrectItem found" on GlassFish V2 & 3 in trunk
2. eclipselink.core.test on H2 in EclipseLink 2.1 org.eclipse.persistence.testing.tests.simultaneous.AppendLockTest.AppendLockTest failed with Exception Description: Fatal error occurred. Internal Exception: junit.framework.AssertionFailedError: Bug 9484687 - deadlock occured
org.eclipse.persistence.testing.tests.jpa.relationships.ExpressionJUnitTestSuite.testLocateWithDoubleArgument_Neg failed on GlassFish V2 & 3 in trunk with following error: Test error: IncorrectItem found junit.framework.AssertionFailedError: Test error: IncorrectItem found at org.eclipse.persistence.testing.tests.jpa.relationships.ExpressionJUnitTestSuite.testLocateWithDoubleArgument_Neg(ExpressionJUnitTestSuite.java:512) at org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBareServer(JUnitTestCase.java:534) at org.eclipse.persistence.testing.framework.server.TestRunnerBean.runTest(TestRunnerBean.java:87) at org.glassfish.ejb.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1052) at org.glassfish.ejb.security.application.EJBSecurityManager.invoke(EJBSecurityManager.java:1124) at com.sun.ejb.containers.BaseContainer.invokeBeanMethod(BaseContainer.java:5243) at com.sun.ejb.EjbInvocation.invokeBeanMethod(EjbInvocation.java:615) at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:797) at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:567) at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doAround(SystemInterceptorProxy.java:157) at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.aroundInvoke(SystemInterceptorProxy.java:139) at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:858) at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:797) at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:367) at com.sun.ejb.containers.BaseContainer.__intercept(BaseContainer.java:5215) at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:5203) at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:201) at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:75) at $Proxy280.runTest(Unknown Source) at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:146) at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:176) at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:682) at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:216) at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1841) at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1695) at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:1078) at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:221) at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:797) at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.dispatch(CorbaMessageMediatorImpl.java:561) at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.doWork(CorbaMessageMediatorImpl.java:2558) at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:492) at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:528)
The following two tests failed with <weblogic-domain-test> on WebLogic 10.3.3 only, the tests passed after reran: 1.org.eclipse.persistence.testing.tests.jpa.advanced.QueryCastTestSuite.testSelectCast Error during postInvoke.; nested exception is: java.lang.Exception: [EJB:011063]Stateless session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method runTest(java.lang.String,java.lang.String,java.util.Properties) of EJB 'TestRunner' either returned or threw an Exception without properly completing a transaction.; nested exception is: java.lang.Exception: [EJB:011063]Stateless session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method runTest(java.lang.String,java.lang.String,java.util.Properties) of EJB 'TestRunner' either returned or threw an Exception without properly completing a transaction 2. org.eclipse.persistence.testing.tests.jpa.advanced.QueryCastTestSuite.testCastInSubselect Error during postInvoke.; nested exception is: java.lang.Exception: [EJB:011063]Stateless session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method runTest(java.lang.String,java.lang.String,java.util.Properties) of EJB 'TestRunner' either returned or threw an Exception without properly completing a transaction.; nested exception is: java.lang.Exception: [EJB:011063]Stateless session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method runTest(java.lang.String,java.lang.String,java.util.Properties) of EJB 'TestRunner' either returned or threw an Exception without properly completing a transaction.
Following six tests in jpql/AdvancedQueryTestSuite and testSetup in jpql/JUnitJPQLComplexTestSuite failed with GlassFish V2 on EclipseLink 2.1 are intermittent. org.eclipse.persistence.testing.tests.jpa.jpql.AdvancedQueryTestSuite (1)testSetup An exception occurred trying clear the cache. (2)testBatchFetchingInheritance Should have been 5 query but was: 1 (3)testMapBatchFetchingJOIN Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist Error Code: 942 (4)testMapBatchFetchingEXISTS Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist Error Code: 942 (5)testMapBatchFetchingIN Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist Error Code: 942 (6)testMapJoinFetching Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist Error Code: 942 org.eclipse.persistence.testing.tests.jpa.jpql.JUnitJPQLComplexTestSuite.testSetup
org.eclipse.persistence.testing.tests.jpa.composite.advanced.testCreateEntityManagerFactory2() failed on WebLogic 10.3.5 with JPA2.0 patch only. It failed at "emf = Persistence.createEntityManagerFactory("default123");", when WebLogic executes this statement, it will list all the persistence providers avaliable in the container, and try to find entity manager with PU name "default123" in each provider, it should not find it and throw PersistenceException, then the test pass. In WebLogic 10.3.5 with JPA2.0 patch, the providers are org.apache.openjpa.persistence.PersistenceProviderImpl, kodo.persistence.PersistenceProviderImpl ,org.eclipse.persistence.jpa.PersistenceProvider. Since openjpa doesn't support composite persistence units, so it throws unexpected "org.apache.openjpa.util.GeneralException: org.xml.sax.SAXException" when trying to load eclipselink-composite-advanced-model-member_1_ejb.jar, so the test terminated and failed. In In WebLogic 10.3.5 without patch, the providers list is kodo.persistence.PersistenceProviderImpl, org.apache.openjpa.persistence.PersistenceProviderImpl and org.eclipse.persistence.jpa.PersistenceProvider. Kodo can handle composite persistence units and throws expected PersistenceException, so the test passed even with unexpected "org.apache.openjpa.util.GeneralException: org.xml.sax.SAXException" from openjpa. So the solution is associate the bug with test result for WebLogic 10.3.5 with JPA2.0 patch, later we will talk with developer to see if we can change the test.
In 2.4, org.eclipse.persistence.testing.tests.jpa.dcn.DCNTestSuite.testUpdate() and org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationJUnitTestSuite.testDDLTablePerClassModelQuery failed with JDK17 intermittently. For example, testUpdate(): It passed in following result: http://ottvm054.ca.oracle.com/eclipselink/2.4/2012-10-25/#certify-jdk17 http://ottvm054.ca.oracle.com/eclipselink/2.4/2012-10-24/#certify-jdk17 It failed in following result: http://ottvm054.ca.oracle.com/eclipselink/2.4/2012-10-30/#certify-jdk17 testDDLTablePerClassModelQuery () It failed in following result: http://ottvm054.ca.oracle.com/eclipselink/2.4/2012-10-24/#certify-jdk17 It passed in following result: http://ottvm054.ca.oracle.com/eclipselink/2.4/2012-10-25/#certify-jdk17 http://ottvm054.ca.oracle.com/eclipselink/2.4/2012-10-30/#certify-jdk17
James made some changes to JTAOptimisticLockExceptionTest in JPQLValidationTestSuite on Oct 30, 2012 as for fix of bug 390352 in master, then the test failed on all servers, later on Nov 1, 2012 he put fix for the failure, as for today's latest result (Nov 8), the test still failed on GlassFish 3.1.2.2, then I sent email to him about the issue, he said: ------------------------------------------------------------------------------- Seems to be a bug in Glassfish 3.1.2. The test is passing on Glassfish 4, so seems like they fixed it. The RollbackException should have the caused by set, but doesn’t seem to in Glassfish 3.1.2. Can you mark it as a known failure? ------------------------------------------------------------------------------- So I record the message here to treat the test failure as known issue. I will update known bug file
recenly, (1)the GlassFish 3.1.2 mysql 5 connector jpa-lrg testing in master and 2.5, several tests in jpa/ddlgeneration and jpa/delimited failed in nightly run, the all tests in these two models passed if I run individual modes in debug run, see ddlgeneration run in master: http://ottvm054.ca.oracle.com/ottvm058/debug/2013-07-31-10.35.44/ see delimited run in master: http://ottvm054.ca.oracle.com/ottvm058/debug/2013-07-31-13.53.54/ (2). DB2 core tests have two or one test failures since we upgrade the DB2 from 9.7 to 10.1. Before 2013-07-05, the two tests passed. After 2013-07-05, the two tests failed in 2.5, two or one tests failed in master. I have checked the transactions between 20130705-35b6757 (Blaise for bug 412336) and 20130706-f712d02(David Minskey bug 412244) in 2.5, nothing is related to failed tests. http://ottvm054.ca.oracle.com/eclipselink/2.5/2013-07-05/index-db.html#certify-db2-10.1-universal http://ottvm054.ca.oracle.com/eclipselink/2.5/2013-07-08/index-db.html#certify-db2-10.1-universal
note: in the debug run, sometimes I got 2 test failures, sometimes I got one test failure. See the latest run in master: http://ottvm054.ca.oracle.com/ottvm057/debug/2013-07-31-14.27.29/
Recently jpa/advanced-multitenant and jpa/xmltest failed in mysql 5.0 connector and derby 10 clientxa in EclipseLink 2.4.3. 1. The error for jpa/advanced-multitenant is: Unknown plain text format. A properly formatted response from a PlainTextActionReporter [exec] always starts with one of these 2 strings: PlainTextActionReporterSUCCESS or PlainTextActionReporterFAILURE. The response we received from the server was not understood: Signature-Version: 1.0 [exec] message: Error occurred during deployment: Exception while preparing t [exec] he app : Exception [EclipseLink-7344] (Eclipse Persistence Services - [exec] 2.4.3.v20130827-330235e): org.eclipse.persistence.exceptions.Validat [exec] ionException A properly formatted response from a PlainTextActionReporter [exec] always starts with one of these 2 strings: PlainTextActionReporterSUCCESS or PlainTextActionReporterFAILURE. The response we received from the server was not understood: Signature-Version: 1.0 [exec] message: Error occurred during deployment: Exception while preparing t [exec] he app : Exception [EclipseLink-7344] (Eclipse Persistence Services - [exec] 2.4.3.v20130827-330235e): org.eclipse.persistence.exceptions.Validat [exec] ionException 2. The error for jpa/xmltest is intermittent. I reran the model individually, all tests passed. So the error in nightly is probably related to failure of other test models.
No intermittent issues in serverside recently, changes have been made.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
