August 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3075) Should be possible to register UserTypes for known property types (classes) in configuration

by Martin Probst (JIRA)

Should be possible to register UserTypes for known property types (classes) in configuration -------------------------------------------------------------------------------------------- Key: HHH-3075 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3075 Project: Hibernate3 Issue Type: Improvement Components: core Environment: n/a Reporter: Martin Probst Priority: Minor Currently, when persisting primitive properties of a class that are not known to Hibernate, there are only cumbersome ways to tell Hibernate that a certain UserType should be used. Good example is Joda Time: <pre> @Entity class MyClass { org.joda.time.DateTime foo; } </pre> .. which will result in ugly binary fields in database. Next try: <pre> @Entity class MyClass { @Type(type = "org.joda.time.contrib.hibernate.PersistentDateTime") org.joda.time.DateTime foo; } </pre> That works, but now I have to specify that on all time fields of all classes. Plus it's different types for different classes, which makes it more messy. And it's simply a string in code, so it's fragile to refactoring, code move, etc. TypeDefs allow a shorter handle for certain types, but don't really address the refactoring issues. A better way might be to allow configurations to register UserTypes for known classes. E.g. have a configuration directive like this: <mappable-type class="org.joda.time.DateTime" usertype="org.joda.time.hibernate.DateTimeType"/> This would allow the classes to stay clean from type mappings and reduce coupling between domain objects and persistence mapping. This might be as easy as allowing the org.hibernate.type.TypeFactory map to be extended at configuration time. -- 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

14 years, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2645) Synchronization bottleneck in EntityModeToTuplizerMapping

by Erik Bergersjö (JIRA)

Synchronization bottleneck in EntityModeToTuplizerMapping --------------------------------------------------------- Key: HHH-2645 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2645 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.4.sp1, 3.2.4, 3.2.3 Environment: Hibernate 3.2.3 (and later), Sun's JDK 1.4.2_12 (server VM) on SunOS 5.10, Oracle 10g R2 Reporter: Erik Bergersjö Priority: Minor We have had a major performance bottleneck in EntityModeToTuplizerMapping with Hibernate version 3.2.3 and the code for that class in 3.2.4sp1 is unchanged. We have found a solution that solves the issue and would like to get it into the real version. I submitted to the user forum first and was asked to create a JIRA issue. The problematic line is: private final Map tuplizers = Collections.synchronizedMap( new SequencedHashMap() ); We have changed it to (using util.concurrent): private final Map tuplizers = new EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap(); This change alone makes our use cases six times faster. The difference is that ConcurrentReaderHashMap handles concurrent readers much better, they don't have to wait for each other. The problem occurs when a high number of threads try to initialize sets (see mapping below). A thread dump showed a high number of threads waiting for the same monitor, see partial stack trace below. The code runs on Sun's JDK 1.4.2_12 (server VM) on SunOS 5.10 and the kernel spends a lot of time handling mutexes with the original implementation. That time disappears from the radar screen with the fixed version. Example mapping for set: [code] <set name="lines" lazy="true" inverse="true" cascade="all-delete-orphan"> <key> <column name="col1" not-null="true" /> <column name="col2" not-null="true" /> </key> <one-to-many class="LineClass" /> </set> [/code] Stack trace (partial): "Thread-108" prio=5 tid=0x05852e90 nid=0x103 waiting for monitor entry [0x3ed7e000..0x3ed7fc28] at java.util.Collections$SynchronizedMap.get(Collections.java:1942) - waiting to lock <0x89d30788> (a java.util.Collections$SynchronizedMap) at org.hibernate.tuple.EntityModeToTuplizerMapping.getTuplizerOrNull(EntityModeToTuplizerMapping.java:53) at org.hibernate.tuple.EntityModeToTuplizerMapping.getTuplizer(EntityModeToTuplizerMapping.java:66) at org.hibernate.type.ComponentType.getPropertyValues(ComponentType.java:353) at org.hibernate.type.ComponentType.isEqual(ComponentType.java:141) at org.hibernate.engine.CollectionKey.equals(CollectionKey.java:50) at java.util.HashMap.eq(HashMap.java:274) at java.util.HashMap.get(HashMap.java:323) at org.hibernate.engine.loading.CollectionLoadContext.getLocalLoadingCollectionEntry(CollectionLoadContext.java:163) at org.hibernate.engine.loading.CollectionLoadContext.locateLoadingCollectionEntry(CollectionLoadContext.java:150) at org.hibernate.engine.loading.CollectionLoadContext.getLoadingCollection(CollectionLoadContext.java:92) at org.hibernate.loader.Loader.readCollectionElement(Loader.java:1003) at org.hibernate.loader.Loader.readCollectionElements(Loader.java:646) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:591) at org.hibernate.loader.Loader.doQuery(Loader.java:701) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.loadCollection(Loader.java:1994) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:565) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentSet.iterator(PersistentSet.java:163) -- 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

14 years, 7 months

8
28
0 / 0

[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

14 years, 7 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2009