October 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3334) Cascading breaks if parent table doesn't have Auto-inc

by Wallace Wadge (JIRA)

Cascading breaks if parent table doesn't have Auto-inc ------------------------------------------------------ Key: HHH-3334 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3334 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.CR1, 3.2.6, 3.2.5, 3.2.4.sp1 Environment: tested on MySql, and hibernate versions (with annotations) v3.2.4 to 3.3.0CR1 Reporter: Wallace Wadge (reposting here from forum) Consider: - a table with an assigned PK (i.e. not auto-increment), let's call this "A" - Another table ("B") linked to the table listed above but with it's PK set to auto-increment. Now if you try to save B with cascading switched on, it will break. From the little debugging I've done it looks like: a) hibernate detects that A needs to be saved first, but puts it into some sort of queue. b) when it hits B, it short-circuits this save queue and tries to save B immediately so as to obtain a PK reference for B. This fails since A hasn't been yet been saved so it's link is still null. Schema used is listed below (MySQL): ---- CREATE DATABASE `jira` /*!40100 DEFAULT CHARACTER SET latin1 */; DROP TABLE IF EXISTS `jira`.`parent`; CREATE TABLE `jira`.`parent` ( `parent_id` int(10) unsigned NOT NULL, PRIMARY KEY (`parent_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; DROP TABLE IF EXISTS `jira`.`child`; CREATE TABLE `jira`.`child` ( `child_id` int(10) unsigned NOT NULL auto_increment, `parent_id` int(10) unsigned NOT NULL, PRIMARY KEY (`child_id`), KEY `FK_child_1` (`parent_id`), CONSTRAINT `FK_child_1` FOREIGN KEY (`parent_id`) REFERENCES `parent` (`parent_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- 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, 10 months

4
22
0 / 0

[Hibernate-JIRA] Created: (HHH-3006) ConcurrentModificationException in AbstractBatcher results in infinite loop

by Stefan Hauk (JIRA)

ConcurrentModificationException in AbstractBatcher results in infinite loop --------------------------------------------------------------------------- Key: HHH-3006 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3006 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3 Environment: Hibernate 3.2.5.ga MySQL 5.0.42 Reporter: Stefan Hauk Priority: Minor Here is a piece of code from org.hibernate.jdbc.AbstractBatcher's closeStatements() method: Iterator iter = resultSetsToClose.iterator(); while ( iter.hasNext() ) { try { logCloseResults(); ( (ResultSet) iter.next() ).close(); } catch (SQLException e) { // no big deal log.warn("Could not close a JDBC result set", e); } catch (Throwable e) { // sybase driver (jConnect) throwing NPE here in certain cases log.warn("Could not close a JDBC result set", e); } } resultSetsToClose.clear(); In case there is a ConcurrentModificationException thrown when iterating over the resultSetsToClose HashSet the exception will be caught by the catch(Throwable) clause. However, the iteration may continue infinitely because of the corrupted HashSet. This pegs one CPU and logs the following stack trace over and over again: 28/11 20:16:50 WARN AbstractBatcher [resin-tcp-connection-myserver:6001-15] Could not close a JDBC result set java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:841) at java.util.HashMap$KeyIterator.next(HashMap.java:877) at org.hibernate.jdbc.AbstractBatcher.closeStatements(AbstractBatcher.java:314) at org.hibernate.jdbc.ConnectionManager.cleanup(ConnectionManager.java:382) at org.hibernate.jdbc.ConnectionManager.close(ConnectionManager.java:324) at org.hibernate.impl.SessionImpl.close(SessionImpl.java:298) at org.springframework.orm.hibernate3.SessionFactoryUtils.closeSession(SessionFactoryUtils.java:774) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.closeSession(OpenSessionInViewFilter.java:252) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:183) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75) at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:70) at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:188) at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:178) at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:229) at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:419) at com.caucho.server.port.TcpConnection.run(TcpConnection.java:389) at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:492) at com.caucho.util.ThreadPool.run(ThreadPool.java:425) at java.lang.Thread.run(Thread.java:595) The catch(Throwable) block was added in Hibernate 3.2.3 if I saw that correctly. Apparently the reason was to catch a NPE thrown by a sybase driver here, but catching Throwable catches more than that and produces this side-effect. Now I do realize that the ConcurrentModificationException might be caused by not using Hibernate in a correct way, but I haven't determined the cause for it yet. However, I do think that Hibernate should fail more gracefully than it currently does. -- 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, 10 months

14
20
0 / 0

[Hibernate-JIRA] Created: (HHH-2708) attribute order-by don't devlared on hibernate-mapping-3.0.dtd

by Sunteya (JIRA)

attribute order-by don't devlared on hibernate-mapping-3.0.dtd -------------------------------------------------------------- Key: HHH-2708 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2708 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Reporter: Sunteya HHH-1414 bug already fixed order-by attribute on the <many-to-many/> element but the dtd file don't allow use order-by attribute. -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-719) Upload Hibernate-Annotations 3.3.1.GA to central maven repository

by Andreas Schildbach (JIRA)

Upload Hibernate-Annotations 3.3.1.GA to central maven repository ----------------------------------------------------------------- Key: ANN-719 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-719 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.1.GA Reporter: Andreas Schildbach Could you upload Hibernate-Annotations 3.3.1.GA to the central maven repository? Would you also add the sources? -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2980) Error "org.hibernate.HibernateException: cannot simultaneously fetch multiple bags" not specific enough

by Dobes Vandermeer (JIRA)

Error "org.hibernate.HibernateException: cannot simultaneously fetch multiple bags" not specific enough ------------------------------------------------------------------------------------------------------- Key: HHH-2980 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2980 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.5 Reporter: Dobes Vandermeer When I get this exception: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags I don't know what to do except google. Why not spruce it up a little to say something like: For class X, multiple collection fields are marked for eager fetching: a, b, c; this is not supported by Hibernate in releases after 3.2.x -- 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, 11 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3191) QueryPlanCache cache size

by Julien Kirch (JIRA)

QueryPlanCache cache size ------------------------- Key: HHH-3191 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3191 Project: Hibernate3 Issue Type: Improvement Components: query-hql Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, all platform Reporter: Julien Kirch On a large application with many (currently 696) named queries in hbm files we have a performance issue with the QueryPlanCache cache size: The SoftLimitMRUCache used in the QueryPlanCache use 128 hard references, the other being soft references, and this number is hardcoded. As we have much more querries in the application, we spend much time in recompiling the same queries when they are evicted from the cache. As the QueryPlanCache has a SessionFactoryImplementor as parameter, adding a new parameter to define the query cache plan size would be trivial; what's your opinion about this ? -- 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, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2431) QueryPlanCache grows without bound. Eventually gets OutOfMemoryException

by Eric Goff (JIRA)

QueryPlanCache grows without bound. Eventually gets OutOfMemoryException -------------------------------------------------------------------------- Key: HHH-2431 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2431 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: all versions, all platforms Reporter: Eric Goff Every time you execute a query, and that query does not match any existing queries in the QueryPlanCache, that query is *always* added to the Query Plan Cache, along with a lot of various antlr stuff. There seems to be no way to control it. Minimally, there should be some sort of heap of query plans where the least used query plan is ejected when the cache reaches it max size. The cache size should, of course, be user configurable. -- 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, 11 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HBX-1000) Problem with PostgreSQL using uppercase letters in tables

by Ruediger Engelberger (JIRA)

Problem with PostgreSQL using uppercase letters in tables --------------------------------------------------------- Key: HBX-1000 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1000 Project: Hibernate Tools Issue Type: Bug Components: reverse-engineer Affects Versions: 3.2.beta11 Environment: Hibernate 3.2.5.ga, Hibernate Tools 3.2.0 beta9a, PostgreSql 8.2, postgresql-8.2-506.jdbc3.jar, Eclipse 3.3.0, all running on Windows XP at the moment (including PostgreSql) Reporter: Ruediger Engelberger I have problems using Hibernate tools when using upper case letters in a PostgreSQL database. I can configure Hibernate Tools for my local PostgreSql installation without any problems. I can access the table structure in the view Hibernate Configurations and do reverse engineering by creating XML mappings and beans. No problem. But when I'm using upper case characters in table names Hibernate Tools can't access the table structures any more. Hibernate Configuration shows the tables, but when I want to see the columns, it doesn't show anything. Reverse engineering also doesn't work any more. So, the following works: TABLE cms_clusterMessage pk_clustermessageid fk_clusternodeid messagetype messagedetail The following doesn't work: TABLE cms_clusterMessage PK_ClusterMessageId FK_ClusterNodeId MessageType MessageDetail I tried to use different JDBC drivers because I thought it could be a bug of the driver. But it wasn't. -- 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, 11 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3478) @NaturalId queries not flushed from cache using EntityManager.remove(); exception results from query

by Elias Ross (JIRA)

@NaturalId queries not flushed from cache using EntityManager.remove(); exception results from query ---------------------------------------------------------------------------------------------------- Key: HHH-3478 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3478 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.0.SP1 Environment: Java 1.5, Maven dependencies: [INFO] (root) [INFO] | \- org.hibernate:hibernate-validator:jar:3.1.0.GA:compile [INFO] +- commons-codec:commons-codec:jar:1.3:compile [INFO] +- javax.persistence:persistence-api:jar:1.0:compile [INFO] +- org.hibernate:hibernate-core:jar:3.3.0.SP1:compile [INFO] | +- antlr:antlr:jar:2.7.6:compile [INFO] | +- commons-collections:commons-collections:jar:3.1:compile [INFO] | \- dom4j:dom4j:jar:1.6.1:compile [INFO] | \- xml-apis:xml-apis:jar:1.0.b2:compile [INFO] +- org.hibernate:hibernate-annotations:jar:3.4.0.GA:compile [INFO] | \- org.hibernate:ejb3-persistence:jar:1.0.2.GA:compile [INFO] +- org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga:compile [INFO] | \- org.hibernate:hibernate:jar:3.2.1.ga:compile [INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile [INFO] | +- asm:asm-attrs:jar:1.5.3:compile [INFO] | +- cglib:cglib:jar:2.1_3:compile [INFO] | \- asm:asm:jar:1.5.3:compile [INFO] +- org.hibernate:hibernate-entitymanager:jar:3.4.0.GA:compile [INFO] | \- javassist:javassist:jar:3.4.GA:compile [INFO] +- javax.transaction:jta:jar:1.0.1B:compile [INFO] +- org.slf4j:slf4j-api:jar:1.5.2:compile [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.2:compile [INFO] +- hsqldb:hsqldb:jar:1.8.0.10:test [INFO] \- junit:junit:jar:4.4:test Reporter: Elias Ross Attachments: Dummy.java, DummyTest.java, persistence.xml See attached test case and entity. Current Result: javax.persistence.EntityNotFoundException: Unable to find com.autodesk.lbs.cs.Dummy with id 1 at org.hibernate.ejb.Ejb3Configuration$Ejb3EntityNotFoundDelegate.handleEntityNotFound(Ejb3Configuration.java:113) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:171) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:223) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:126) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:905) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:873) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:590) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:219) at org.hibernate.cache.StandardQueryCache.get(StandardQueryCache.java:155) at org.hibernate.loader.Loader.getResultFromQueryCache(Loader.java:2184) at org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2147) at org.hibernate.loader.Loader.list(Loader.java:2117) 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 org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328) at com.autodesk.lbs.cs.DummyTest.naturalKeyCachedQuery(DummyTest.java:69) at com.autodesk.lbs.cs.DummyTest.naturalKeyCachedQuery(DummyTest.java:61) at com.autodesk.lbs.cs.DummyTest.testQuery(DummyTest.java:49) It's expected that a cache invalidation occurs with an entity's natural key when it is removed. I'll investigate a solution. -- 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, 11 months

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2510) override equals()/hashCode() in AliasToBeanResultTransformer

by Maxim Gordienko (JIRA)

override equals()/hashCode() in AliasToBeanResultTransformer ------------------------------------------------------------ Key: HHH-2510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2510 Project: Hibernate3 Type: Improvement Versions: 3.2.2 Reporter: Maxim Gordienko AliasToBeanResultTransformer whould override equals()/hashCode() to allow convenient second level query caching. Now the only way is to maintain single transformer instance per bean class to allow query cache hit. -- 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, 11 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2008