November 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3050) Convert usage of Hibernate's FastHashMap to ConcurrentHashMap (Java 1.5)

by Gail Badner (JIRA)

Convert usage of Hibernate's FastHashMap to ConcurrentHashMap (Java 1.5) ------------------------------------------------------------------------ Key: HHH-3050 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3050 Project: Hibernate3 Issue Type: Improvement Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.3 The performance test attached to HHH-2645 shows that java.util.concurrent.ConcurrentHashMap (introduced in Java 1.5) performs nearly as well as org.hibernate.util.FastHashMap. Hibernate needs to move to Java 1.5 before this can be done. As noted in HHH-2645, it might be worthwhile to convert usages of FastHashMap to ConcurrentHashMap so that FastHashMap does not need to be maintained. -- 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

15 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (ANN-820) TypeDef does not work when used on @Embeddable or @MappedSuperClass classes.

by Ted Bergeron (JIRA)

TypeDef does not work when used on @Embeddable or @MappedSuperClass classes. ---------------------------------------------------------------------------- Key: ANN-820 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-820 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Environment: Oracle 11, hibernate 3.4.0 GA Reporter: Ted Bergeron @TypeDefs({ @TypeDef( name = "status", typeClass = EnumUserType.class, parameters = {@Parameter(name = "enumClass", value = "com.acme.common.model.Status")} ) }) I declare various @TypeDefs such as this. They all work fine when used in @Entity classes. When used in a @MappedSuperclass, or an @Embeddable, they fail. I see from the docs that these are global and double checked that I do not have any duplicate @TypeDef definitions. -- 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

15 years, 11 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-168) Add the ability to disable automatic indexing both on a per index level and programmatically

by Eric Winter (JIRA)

Add the ability to disable automatic indexing both on a per index level and programmatically -------------------------------------------------------------------------------------------- Key: HSEARCH-168 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-168 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Eric Winter Priority: Minor It is very resticitive in an application that has multiple indexes to only allow the disabling of automatic indexing on an application wide level (or at least SessionFactory wide...). I can see it being very useful to have auto indexing on a per index basis. Also, it would be nice to be able to turn auto indexing off and on programmatically using something like Search.setAutoIndexing("myIndex", false); //per index and Search.setAutoIndexing(false); //global -- 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

15 years, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-846) Infinite loop occurs while doing findById on a Parent domain Object having OneToMany relationship with child domain with composite primary key

by RAMESH BABU NL (JIRA)

Infinite loop occurs while doing findById on a Parent domain Object having OneToMany relationship with child domain with composite primary key ---------------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-846 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-846 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.4.0.GA Environment: Hibernate Annotations 3.4.0.GA, HSqlDB and Oracle Reporter: RAMESH BABU NL Attachments: Organization.java, OrganizationApplications.java, OrganizationApplicationsPK.java We are using Hibernate annotations version 3.4.0.G.A We are establishing a OneToMany relationship using the annotation @OnetoMany for a Parent and Child domain objects where the child domain has a composite primary key. We have two domain objects Organization [Parent] OrganizationApplications [Child] We want to have a OnetoMany relationship between Organization and OrganizationApplications. As shown below OrganizationApplications contains a composite primary key, of two columns(Organization Id, ApplicationId[foreignkey from other table called APPLICATIONS]) Organizations.java ------------------- @OneToMany(targetEntity=gov.osc.enrollment.backend.domain.OrganizationApplications.class, cascade=CascadeType.ALL, fetch = FetchType.EAGER, mappedBy="id.organization") private Set<OrganizationApplications> organizationApps = new HashSet<OrganizationApplications>(); OrganizationApplications.java --------------------------------------------------------------------- public class OrganizationApplications extends EnvelopeInfo implements Serializable { private static final long serialVersionUID = 1L; @EmbeddedId private OrganizationApplicationsPK id; public OrganizationApplicationsPK getId() { return id; } public void setId(OrganizationApplicationsPK id) { this.id = id; } OrganizationApplicationsPK.java --------------------------------------------------------------------- @Embeddable public class OrganizationApplicationsPK implements Serializable { private static final Long serialVersionUID = 1L; public OrganizationApplicationsPK() { super(); } @ManyToOne @JoinColumn(name="APPLICATION_ID",nullable=false) private Applications application; @ManyToOne(targetEntity=gov.osc.enrollment.backend.domain.Organization.class, cascade=CascadeType.ALL) @JoinColumn(name="ORGANIZATION_ID", referencedColumnName="ORGANIZATION_ID", nullable=false, insertable=true, updatable=true) private Organization organization; public Applications getApplication() { return application; } public void setApplication(Applications application) { this.application = application; } public Organization getOrganization() { return organization; } public void setOrganization(Organization organization) { this.organization = organization; } @Override public boolean equals(Object o) { if (o == this) { return true; } if ( ! (o instanceof OrganizationApplicationsPK)) { return false; } OrganizationApplicationsPK other = (OrganizationApplicationsPK) o; return (this.getOrganization().getId() == other.getOrganization().getId()) && (this.getApplication().getId() == other.getApplication().getId()); } @Override public int hashCode() { final int prime = 31; int hash = 17; hash = hash * prime + ((int) (this.getOrganization().getId() ^ (this.getOrganization().getId() >>> 32))); hash = hash * prime + ((int) (this.getApplication().getId() ^ (this.getApplication().getId() >>> 32))); return hash; } } Please see the attached java files for complete code and also the exception stack trace. Questions: 1. When we do a findById query on Organization table the system goes into infinite loop and never gets out . How ever we are able to insert a record in Organization and its child OrganizationApplications. 2. In the Organization.java domain, if you notice we are using mappedby="id.organization". Is this a valid mapping ? If not why does this parameter work for insert and not for a entityManager.findById, doing so leads to infinite loop. -- 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

15 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3884) NPE with mutable Natuarl Id's

by Michael Kopp (JIRA)

NPE with mutable Natuarl Id's ----------------------------- Key: HHH-3884 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3884 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.2 Reporter: Michael Kopp When saving an entity with a mutable natural id hibernate throws the following NPE. java.lang.NullPointerException at org.hibernate.engine.StatefulPersistenceContext.getNaturalIdSnapshot(StatefulPersistenceContext.java:267) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:78) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:162) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:113) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) I checked the code and found the reason: - getNaturalIdSnapshot calls getDatabaseSnapshot and checks the result for NO_ROW but not for null - getDatabaseSnapshot will never return NO_ROW but null if nothing was found hence getNaturalIdSnapshot will produce a NPE if the entity is not in the database already. the fix is simple: change: Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == NO_ROW ) { return null; } to Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == null ) { return null; } This is still there in trunk as well! -- 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

15 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3068) Update of an entity with immutable natural-id and many-to-one relation seems to fail

by Pascal Cohen (JIRA)

Update of an entity with immutable natural-id and many-to-one relation seems to fail ------------------------------------------------------------------------------------ Key: HHH-3068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3068 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Linux Fedora 32bits Postgres 8.2.5 Reporter: Pascal Cohen Priority: Minor I have posted in the forum the following question and someone seems to confirm this might be a bug. http://forum.hibernate.org/viewtopic.php?t=982385&highlight= Thanks in advance for advice -- 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

15 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2041) Update with unaltered natural-id fails

by Jim Pease (JIRA)

Update with unaltered natural-id fails -------------------------------------- Key: HHH-2041 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2041 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: hibernate-3.1.3, mysql-4.1.12 Reporter: Jim Pease This may be a duplicate of http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574. Getting following error: caused by: org.hibernate.HibernateException: immutable natural identifier of an instance of edu.syr.lsb.gmt.impl.LinkImpl was altered at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:80) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:155) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:106) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) ... This is occurring without modifications to the natural identifier, which is mapped as follows: <natural-id> <property name="activityRef" column="ACTIVITY_REF" length="255" not-null="true" /> <many-to-one name="goal" class="GoalImpl" column="GOAL_ID" not-null="true" cascade="none" /> </natural-id> -- 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

15 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3256) OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart)

by Tom Muldoon (JIRA)

OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart) -------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3256 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3256 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, MySQL 5 Reporter: Tom Muldoon After a JBoss restart, the in-memory hiValue is -1. As such, the callback.getNextValue( ) method is invoked twice. With an increment size of 50 and a current database next_val of 10000, the PooledOptimizer.generate method returns a value of 10000 (as expected) and sets the in memory hiValue to 10050 (also as expected), however, it sets the db next_val to 10100. Shouldn't the db next_val be kept in sync with the in-memory hiValue (i.e. 10050)? -- 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

15 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-324) @DynamicBoost(BoostStrategy.class)

by Emmanuel Bernard (JIRA)

@DynamicBoost(BoostStrategy.class) ---------------------------------- Key: HSEARCH-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-324 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.1, 3.2.0 This sounds like an interesting feature. We could do something very similar to the new AnalyzerDiscriminator approach. The use case is explained http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78... Need some analysis before the jump We can do that in 3.1.1, but no hard pressure. -- 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

15 years, 11 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4065) Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed

by Nicklas Nordborg (JIRA)

Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed -------------------------------------------------------------------------------------------------- Key: HHH-4065 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4065 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Environment: Hibernate 3.3.2 Reporter: Nicklas Nordborg Attachments: trace.txt I think that maybe the fix for HHH-530 has introduced a problem with filters that has a collection-type parameter. If the number of parameters in that collection changes during the lifetime of a SessionFactory the SQL that is used becomes incorrect and either has too many or too few parameter placeholders (eg. '?') in the SQL. There was no problem in Hibernate 3.3.1. A typical error message is: java.sql.SQLException: Parameter index out of bounds. 2 is not between valid values of 1 and 1 Below is some pseudo-code that shows what happens when the number of values in a collection is increased from 1 to 2. The 'memberOf' is a simple filter on the `id` column: `id` IN (:items) String hql = "select n from NewsData n"; List idList = new ArrayList(); idList.add(1); Session s = .... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // SQL: select .... `News` newsdata0_ where newsdata0_.`id` IN (?) s.close(); idList.add(2); s = ... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // <--- error here with 3.3.2 but works with 3.3.1 // SQL (3.3.2): select .... `News` newsdata0_ where newsdata0_.`id` IN (?) // SQL (3.3.1): select .... `News` newsdata0_ where newsdata0_.`id` IN (?, ?) I am attaching a file with TRACE-level output from both Hibernate 3.3.2 and 3.3.1. The relevant difference seems to be that in Hibernate 3.3.2 the query plan is cached with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (?)' but in Hibernate 3.3.1 with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (:memberOf.items)' -- 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

15 years, 11 months

5
14
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2009