[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6020) Move to JBossTS caused some test failures in hibernate-envers
Steve Ebersole (JIRA)
noreply at atlassian.com
Tue Aug 30 15:51:03 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43407#comment-43407 ]
Steve Ebersole commented on HHH-6020:
-------------------------------------
# This never failed prior to the move to {{JBossTS}}. Granted that does not unequivocally means {{JBossTS}} is at fault, but its smoke and where there is smoke there is a high likelihood there will be fire.
# The auto-commit variable in Hibernate is consumed by the {{ConnectionProvider}}. Now it is possible that H2 is not being made properly aware that it is a data source. I am not completely familiar enough with that test to know what {{ConnectionProvider}} it uses etc.
> Move to JBossTS caused some test failures in hibernate-envers
> -------------------------------------------------------------
>
> Key: HHH-6020
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6020
> Project: Hibernate Core
> Issue Type: Bug
> Components: envers
> Reporter: Steve Ebersole
> Assignee: Gail Badner
> Fix For: 4.0.0.next
>
> Attachments: JTA_Transaction_Test.patch
>
> Time Spent: 31m
> Remaining Estimate: 0h
>
> Specifically there is 1 tests that fails in both configurations for a total of 2 failures. The test class is {{org.hibernate.envers.test.integration.jta.JtaTransaction}}. The failure says:
> {noformat}
> null
> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:110)
> at org.hibernate.service.internal.ServiceInitializer.configureService(ServiceInitializer.java:141)
> at org.hibernate.service.internal.ServiceInitializer.initializeService(ServiceInitializer.java:108)
> at org.hibernate.service.internal.ServiceRegistryImpl.getServiceInternal(ServiceRegistryImpl.java:119)
> at org.hibernate.service.internal.proxy.javassist.ServiceProxyFactoryImpl$ServiceProxyMethodInterceptor.invoke(ServiceProxyFactoryImpl.java:114)
> at org.hibernate.engine.jdbc.spi.JdbcServices_$$_javassist_0.getExtractedMetaDataSupport(JdbcServices_$$_javassist_0.java)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:77)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2848)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2844)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1825)
> at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:77)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:888)
> at org.hibernate.envers.test.AbstractEntityTest.init(AbstractEntityTest.java:123)
> at org.hibernate.envers.test.AbstractEntityTest.init(AbstractEntityTest.java:97)
> ...
> {noformat}
> JdbcServicesImpl.java:110 is a simple attempt to use the {{java.sql.Connection}} returned by the configured {{org.hibernate.service.jdbc.connections.spi.ConnectionProvider}}:
> {code}
> Connection conn = connectionProvider.getConnection();
> try {
> DatabaseMetaData meta = conn.getMetaData(); // <- this is line 110
> ...
> {code}
--
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