May 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6223) connection leak in entitymanager and annotation's testsuite

by Strong Liu (JIRA)

connection leak in entitymanager and annotation's testsuite ----------------------------------------------------------- Key: HHH-6223 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6223 Project: Hibernate Core Issue Type: Bug Components: annotations, entity-manager Affects Versions: 3.6.4 Reporter: Strong Liu Priority: Minor Fix For: 3.6.5 lots of entitymanager's tests fail due to can't get connection, and i found org.hibernate.testing.junit.functional.annotations.HibernateTestCase#closeResources is only be called when a test throws exception... thus, for each succeeded test, the session factory will not be closed when it is finished. and due to after each test finishes, we use SchemaExport, which opens a new connection, to drop tables, so this connection will be left open -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1481) any mapping with composite id-type does not work

by Leandro Subils (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1481?page=c... ] Leandro Subils commented on HHH-1481: ------------------------------------- Any news? > any mapping with composite id-type does not work > ------------------------------------------------ > > Key: HHH-1481 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1481 > Project: Hibernate Core > Issue Type: Patch > Affects Versions: 3.0 alpha, 3.0 beta 1, 3.0 beta 2, 3.0 beta 3, 3.0 beta 4, 3.0 rc 1, 3.0 final, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.1 beta 1, 3.1 beta 2, 3.1 rc 1, 3.1 rc2, 3.1 rc3, 3.1, 3.1.1, 3.1.2, 3.2.0.alpha1, 3.1.3, 3.6.0 > Environment: Hibernate 3.1.2 > Reporter: Michael Matt > Attachments: patch.zip > > Original Estimate: 10m > Remaining Estimate: 10m > > Any mapping with composite id-type throws MappingException 'property mapping has wrong number of columns'. > The zipped patch file contains: > -bugfix for AnyType.java > - testcases any mapping with simple id-type and composite id-type -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1673) hql parsed with exception (with clause)

by Nicolas Gavard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1673?page=c... ] Nicolas Gavard commented on HHH-1673: ------------------------------------- This isssue is always a real problem. Is there anybody who can explain why the provided patch is not added to an official version ? Thank you for any comment on this. > hql parsed with exception (with clause) > --------------------------------------- > > Key: HHH-1673 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1673 > Project: Hibernate Core > Issue Type: Deprecation > Components: query-hql > Affects Versions: 3.1.3, 3.5.3 > Reporter: Tomasz Bech > Attachments: HHH-1673.patch, HHH-1673.patch > > > The 'improvement' bug fix: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1520 > has broken working functionality: > I found that after switching to 3.1.3 following construction is not working any longer: > (FootnoteTypeBO has collection 'descriptions' and reference to languageBO) > from FootnoteTypeBO as o > left outer join o.descriptions as t1 > with (t1.language in (select loid from LanguageBO where name = 'aa')) > --> exception: 'with-clause referenced two different from-clause elements'. > There is no implicit join as dewscribed in main anomaly, so it shouldn't cause the problem. So now there is no way to write correct hql/sql, and I don't see any workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6220) Running out of memory for large operation with many native SQL queries because BulkOperationCleanupAction are not freed until transaction close

by Dobes Vandermeer (JIRA)

Running out of memory for large operation with many native SQL queries because BulkOperationCleanupAction are not freed until transaction close ----------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6220 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6220 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.3 Reporter: Dobes Vandermeer When running a long job which performs many SQL queries I eventually run out of memory. This happens because the NativeSQLQueryPlan appends an action to the post-transaction action queue for each native SQL query that I run, and these cleanup operations seem to use a decent amount of memory. There is no clear means by which these objects can be cleaned up besides closing and re-initiating a database transaction. This makes large database transactions that use native SQL queries impossible to write, without splitting them up (which in our case is not desirable). The other workaround is to use JDBC directly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3839) Using Criteria.setMaxResults gives a MySQLSyntaxErrorException

by Kevin DIMEY (JIRA)

Using Criteria.setMaxResults gives a MySQLSyntaxErrorException -------------------------------------------------------------- Key: HHH-3839 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3839 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: MySQL 5.0.51a Reporter: Kevin DIMEY Attachments: hibernate.cfg.xml Hi, When trying to limit the number of rows returned by Criteria.list() method, exception is thrown about bad SQL grammar. The "limit" SQL statement is put just after the select keyword. It should be placed at the end of the request. Moreover, it seems there is no coma between the start row and the amount of objects to retrieve. Here is the method called : session.createCriteria(Etude.class).setFirstResult(5).setMaxResults(10).list(); I get the same issue while using only setMaxResults, it puts the "top" keyword just after the "select" one. Here is the request generated and the stack trace : Hibernate: select limit ? ? this_.id as id7_6_, this_.avorte_id as avorte11_7_6_, this_.confidentielle as confiden2_7_6_, this_.contact_id as contact12_7_6_, this_.created_at as created3_7_6_, this_.date_fin as date4_7_6_, this_.date_signature as date5_7_6_, this_.date_sollicitation as date6_7_6_, this_.entreprise_id as entreprise13_7_6_, this_.etat_code as etat7_7_6_, this_.numero as numero7_6_, this_.sujet as sujet7_6_, this_.updated_at as updated10_7_6_, avortement2_.id as id1_0_, avortement2_.created_at as created2_1_0_, avortement2_.created_by as created3_1_0_, avortement2_.raison as raison1_0_, contact3_.id as id2_1_, contact3_.adresse_id as adresse18_2_1_, contact3_.civilite_code as civilite2_2_1_, contact3_.connu_par_code as connu3_2_1_, contact3_.connu_par_detail as connu4_2_1_, contact3_.created_at as created5_2_1_, contact3_.entreprise_id as entreprise19_2_1_, contact3_.fax as fax2_1_, contact3_.fonction as fonction2_1_, contact3_.mail as mail2_1_, contact3_.news_dernier_envoi as news9_2_1_, contact3_.news_desinscrit as news10_2_1_, contact3_.nom as nom2_1_, contact3_.parti as parti2_1_, contact3_.prenom as prenom2_1_, contact3_.service_code as service14_2_1_, contact3_.tel_fixe as tel15_2_1_, contact3_.tel_portable as tel16_2_1_, contact3_.updated_at as updated17_2_1_, adresse4_.id as id0_2_, adresse4_.adresse1 as adresse2_0_2_, adresse4_.adresse2 as adresse3_0_2_, adresse4_.adresse3 as adresse4_0_2_, adresse4_.code_postal as code5_0_2_, adresse4_.ville as ville0_2_, entreprise5_.id as id5_3_, entreprise5_.adresse_id as adresse14_5_3_, entreprise5_.created_at as created2_5_3_, entreprise5_.disparue as disparue5_3_, entreprise5_.domaine_code as domaine4_5_3_, entreprise5_.effectif_code as effectif5_5_3_, entreprise5_.etat_code as etat6_5_3_, entreprise5_.fax as fax5_3_, entreprise5_.nom as nom5_3_, entreprise5_.num_siret as num9_5_3_, entreprise5_.particulier as particu10_5_3_, entreprise5_.site_web as site11_5_3_, entreprise5_.tel as tel5_3_, entreprise5_.updated_at as updated13_5_3_, adresse6_.id as id0_4_, adresse6_.adresse1 as adresse2_0_4_, adresse6_.adresse2 as adresse3_0_4_, adresse6_.adresse3 as adresse4_0_4_, adresse6_.code_postal as code5_0_4_, adresse6_.ville as ville0_4_, entreprise7_.id as id5_5_, entreprise7_.adresse_id as adresse14_5_5_, entreprise7_.created_at as created2_5_5_, entreprise7_.disparue as disparue5_5_, entreprise7_.domaine_code as domaine4_5_5_, entreprise7_.effectif_code as effectif5_5_5_, entreprise7_.etat_code as etat6_5_5_, entreprise7_.fax as fax5_5_, entreprise7_.nom as nom5_5_, entreprise7_.num_siret as num9_5_5_, entreprise7_.particulier as particu10_5_5_, entreprise7_.site_web as site11_5_5_, entreprise7_.tel as tel5_5_, entreprise7_.updated_at as updated13_5_5_ from etude this_ left outer join avortement avortement2_ on this_.avorte_id=avortement2_.id left outer join contact contact3_ on this_.contact_id=contact3_.id left outer join adresse adresse4_ on contact3_.adresse_id=adresse4_.id left outer join entreprise entreprise5_ on contact3_.entreprise_id=entreprise5_.id left outer join adresse adresse6_ on entreprise5_.adresse_id=adresse6_.id left outer join entreprise entreprise7_ on this_.entreprise_id=entreprise7_.id 29 mars 2009 00:52:29 org.hibernate.util.JDBCExceptionReporter logExceptions ATTENTION: SQL Error: 1064, SQLState: 42000 29 mars 2009 00:52:29 org.hibernate.util.JDBCExceptionReporter logExceptions GRAVE: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'limit 5 10 this_.id as id7_6_, this_.avorte_id as avorte11_7_6_, this_.confident' at line 1 29 mars 2009 00:52:29 org.apache.catalina.core.ApplicationDispatcher invoke GRAVE: "Servlet.service()" pour la servlet jsp a lancï¿½ une exception com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'limit 5 10 this_.id as id7_6_, this_.avorte_id as avorte11_7_6_, this_.confident' at line 1 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.Util.getInstance(Util.java:381) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3515) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3447) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1951) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2101) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2554) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1761) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1912) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) at easytic.support.EtudesSupport$EtudesList.getList(EtudesSupport.java:41) I've attached my hibernate.cfg.xml. This issue seemed resolved in 3.2.5 : http://opensource.atlassian.com/projects/hibernate/browse/HHH-2954 but I got it with 3.3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5649) improve eclipse support with migration to gradle

by Strong Liu (JIRA)

improve eclipse support with migration to gradle ------------------------------------------------ Key: HHH-5649 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5649 Project: Hibernate Core Issue Type: Improvement Reporter: Strong Liu Assignee: Strong Liu Fix For: 4.x currently, I found the following problems when using gradle to generate the eclipse project metadata files: * [GRADLE-1132|http://jira.codehaus.org/browse/GRADLE-1132] Gradle should generate .settings/org.eclipse.jdt.core.prefs this means you may need set the project's compile level manually, ATM, jdk6 * [GRADLE-1074|http://jira.codehaus.org/browse/GRADLE-1074] Add eclipse variables to workspace. the .classpath generated by gradle uses GRADLE_CACHE variable, and this need be added manually, just point it to your $user.home/.gradle/cache * jacc and ant are not in core's classpath these two, (and actually others, such validtion, cglib, but these are added to both "provided" and "testRuntime" configuration) are only in the custom "provided" configuration, by default, eclipse plugin don't know how to deal with a customer configuration. * hibernate-core/src/main/antlr is incorrectly added into classpath * entitymanager's generate-src is not added into classpath -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5598) sybase integration improvement

by Strong Liu (JIRA)

sybase integration improvement ------------------------------ Key: HHH-5598 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5598 Project: Hibernate Core Issue Type: Improvement Components: core Environment: sybase Reporter: Strong Liu Assignee: Strong Liu Those were included. alias length union all support cross join support (back out as Sybase 11 dialect) GUID support Additional UDF functionality and keywords more details please go to http://community.jboss.org/wiki/HibernateSybaseintegration -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6133) generate enhance (create a new one) the Jandex annotation for orm.xml

by Strong Liu (JIRA)

generate enhance (create a new one) the Jandex annotation for orm.xml ---------------------------------------------------------------------- Key: HHH-6133 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6133 Project: Hibernate Core Issue Type: Sub-task Components: annotations, metamodel Reporter: Strong Liu Assignee: Strong Liu Fix For: 4.0.0.Alpha3 creating mock annotations from orm.xml var jandex -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4770) Wrong class property type, when access="field" is specified. The HbmBinder and the method setTypeUsingReflection() of the interface org.hibernate.mapping.Value does not use the property "access" settings (field/property/etc...)

by Peter Fassev (JIRA)

Wrong class property type, when access="field" is specified. The HbmBinder and the method setTypeUsingReflection() of the interface org.hibernate.mapping.Value does not use the property "access" settings (field/property/etc...) ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-4770 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4770 Project: Hibernate Core Issue Type: Bug Components: core, metamodel Affects Versions: 3.5.0-Beta-2, 3.3.2 Reporter: Peter Fassev Attachments: ReflectionTest.zip Hibernate provides a possibility to define different access to the class properties for instance trough class methods (access="property") or directly to fields (access="field"). This information is not used during the initialization of the subclasses of the org.hibernate.mapping.Value (see SimpleValue and ToOne). The Value interface provides a method called setTypeUsingReflection(String className, String propertyName) with only two parameters. Some subclasses like SimpleValue and ToOne are calling the ReflectHelper.reflectedPropertyClass(className, propertyName). The ReflectHelper uses first the BASIC_PROPERTY_ACCESSOR, which always returns the type of the class method. Only if there is no such method, the type of the class field is returned. It does not distinguish between "property" and "field" access. Here is the Method from the ReflectHelper: org.hibernate.util.ReflectHelper: private static Getter getter(Class clazz, String name) throws MappingException { try { return BASIC_PROPERTY_ACCESSOR.getGetter( clazz, name ); } catch ( PropertyNotFoundException pnfe ) { return DIRECT_PROPERTY_ACCESSOR.getGetter( clazz, name ); } } In the case the declared method returns a different type as the declared field Hibernate calculates a wrong type for the fild. Consider the following class with a hidden field "rejected" of type "Date" and a method "isRecected()" of type boolean: class Item { private Date rejected; public void doReject() { rejected = new Date(); } public boolean isRejected() { return rejected != null; } } This type of the rejected field will be recognized by Hibernate as "boolean", even if the field access is defined to be "access=field". By running the ReflectionTestCase you will get an exception: "java.util.Date cannot be cast to java.lang.Boolean". Proposed Resolution: 1) The method org.hibernate.mapping.Value. setTypeUsingReflection needs a new parameter, which provides the access type of the property. 2) The class org.hibernate.mapping.HbmBinder must bind the access attribute of the property prior of calling this method, which is currently not the case (see the method HbmBinder.createProperty()). 3) The classess SimpleValue and ToOne should either use the PropertyAccessorFactory or the ReflectHelper should be extended to handle the access type of the field. Regards PF -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (OGM-65) Support pure Infinispan client mode for Hibernate OGM

by Emmanuel Bernard (JIRA)

Support pure Infinispan client mode for Hibernate OGM ----------------------------------------------------- Key: OGM-65 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-65 Project: Hibernate OGM Issue Type: New Feature Reporter: Emmanuel Bernard There are several levels at play: - allow an OGM client to not join the grid as a full fledge node - support transactions over hotrod (including suspend and co) - support query over hotrod (ie ability to pass the Teiid query via HotRod and let Teiid nodes run on the Infinispan grid) The latest is not fleshed out though and will require refinement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2011