[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6700) mysql test failures

Gail Badner (JIRA) noreply at atlassian.com
Thu Nov 10 07:06:24 EST 2011


    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44285#comment-44285 ] 

Gail Badner commented on HHH-6700:
----------------------------------

I found out why org.hibernate.test.tm.CMTTest.testConcurrentCachedDirtyQueries is getting an unexpected second-level cache hit.

org.hibernate.testing.cache.BaseRegion.getTimeout() returns Timestamper.ONE_MS * 600000.

Timestamper.ONE_MS is 4095. The product is 2457000000, which overflows the int return value, so a negative timeout is returned. As a result, the update timestamp ends up being before the cached query result timestamp. Hibernate assumes (erroneously) that the cached query results are up-to-date. The cache hit that caused the test failure happened when resolving the IDs returned by the cached results. 

Changing BaseRegion.getTimeout() to return Timestamper.ONE_MS * 60000 gets past that assertion, but later ones fail. I'm working my way through those.

> mysql test failures
> -------------------
>
>                 Key: HHH-6700
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6700
>             Project: Hibernate Core
>          Issue Type: Sub-task
>         Environment: MySql 51
>            Reporter: Strong Liu
>
> org.hibernate.test.hql.ASTParserLoadingTest.testJPAQLQualifiedIdentificationVariablesControl 	
> org.hibernate.test.hql.ASTParserLoadingTest.testPaginationWithPolymorphicQuery 	
> org.hibernate.test.hql.ASTParserLoadingTest.testImplicitPolymorphism 	
> org.hibernate.test.hql.ASTParserLoadingTest.testCachedJoinedAndJoinFetchedManyToOne 	
> org.hibernate.test.hql.ASTParserLoadingTest.testCachedJoinedAndJoinFetchedOneToMany 	
> org.hibernate.test.id.uuid.sqlrep.sqlbinary.UUIDBinaryTest.testUsage 	
> org.hibernate.test.id.uuid.strategy.CustomStrategyTest.testUsage 	
> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest.testLazy 	
> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest.testCustomColumnReadAndWrite 	
> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest.testFetchAll 	
> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest.testLazyManyToOne 	
> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest.testPropertyInitialized 	
> org.hibernate.test.querycache.QueryCacheTest.testCaseInsensitiveComparison 	
> org.hibernate.test.sql.hand.query.NativeSQLQueriesTest.testTextTypeInSQLQuery 	
> org.hibernate.test.sql.hand.query.NativeSQLQueriesTest.testImageTypeInSQLQuery 	
> org.hibernate.test.tm.CMTTest.testConcurrentCachedDirtyQueries 	
> org.hibernate.test.sql.hand.custom.mysql.MySQLCustomSQLTest.testScalarStoredProcedure 	
> org.hibernate.test.sql.hand.custom.mysql.MySQLCustomSQLTest.testParameterHandling 	
> org.hibernate.test.sql.hand.custom.mysql.MySQLCustomSQLTest.testEntityStoredProcedure 	
> org.hibernate.test.sql.hand.custom.mysql.MySQLCustomSQLTest.testHandSQL 	

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list