October 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-513) Hibernate Search 3.2.0.CR1 listeners cause long delays when indexing entities saved in different transactions

by Florin Haizea (JIRA)

Hibernate Search 3.2.0.CR1 listeners cause long delays when indexing entities saved in different transactions ------------------------------------------------------------------------------------------------------------- Key: HSEARCH-513 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.CR1 Environment: Hibernate 3.5.1-Final Spring 3.0.2 MySQL Connector 5.1.6 Reporter: Florin Haizea Attachments: HibernateSearchJira.zip I have 3 entities Person, Event and ParentOfBirthEvent. I save about 8000 Person objects in batches of 20, each batch is being saved in a different transaction. After a sufficient number of entities have been persisted (the saving and indexing of initial batches takes between150ms and 500ms) the indexing of the entities that are saved in some of the following batches takes a very large amount of time (sometime even minutes for a whole batch). The problem is that in order for these delays to appear there has to be a certain relationship between the objects saved in the current batch and objects saved in previous batches. The only way in which I can reproduce this 100% is by importing a file (which was submitted by one of the users of our app), creating entities based on the data in that file and saving the entities in batches of 20. When I reach batch number 273 or so the indexing starts taking a lot of time. If I removed the @IndexedEmbedded annotation from the "parent" field in the ParentOfBirthEvent class the problem is solved. Also, if I removed all the hibernate search listeners from the sessionFactory the problem is solved. -- 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

7
68
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-570) Optimize the o^2 loop in DocumentBuilderIndexedEntity.addWorkToQueue

by Sanne Grinovero (JIRA)

Optimize the o^2 loop in DocumentBuilderIndexedEntity.addWorkToQueue -------------------------------------------------------------------- Key: HSEARCH-570 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-570 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.3.0.Alpha1, 3.2.1, 3.2.0.Final Reporter: Sanne Grinovero Fix For: 3.3.0 there's a long-standing comment in the method: bq. //TODO with the caller loop we are in a n^2: optimize it using a HashMap for work recognition Apparently it has a critical impact in some scenarios: [this forum post|https://forum.hibernate.org/viewtopic.php?f=9&t=1006054] mentions the algorithm "running for days" in a 1000 elements change in a single transaction. -- 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
8
0 / 0

[Hibernate-JIRA] Created: (METAGEN-29) Embedded generic types not supported by metamodel generator

by Adrian Hummel (JIRA)

Embedded generic types not supported by metamodel generator ----------------------------------------------------------- Key: METAGEN-29 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-29 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.0.0-CR-1 Environment: Hibernate 3.5.0-CR-2 Reporter: Adrian Hummel Assignee: Hardy Ferentschik Priority: Critical Attachments: bugreport.zip Scenario: I have a @MappedSuperclass defining an abstract entity. This class has a technical primary key and a business identity. The business identity is realized by means of a generic embeddable (e.g. for a Customer class there is a corresponding CustomerId class for its business identity). The JPAMetaModelEntityProcessor does generate the AbstractEntity_ class but does only include the primary key field but omits the generic field for the business identity (which leads to subsequent errors when accessing this field using a CriteriaBuilder). Attached a mini project with a test case which illustrates the problem. -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4539) Make UPPER and LOWER work on MS SQL Server text and ntext columns

by Sergiu Dumitriu (JIRA)

Make UPPER and LOWER work on MS SQL Server text and ntext columns ----------------------------------------------------------------- Key: HHH-4539 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4539 Project: Hibernate Core Issue Type: Improvement Components: query-sql Affects Versions: 3.3.2 Environment: MS SQL Server Reporter: Sergiu Dumitriu Trying to use UPPER or LOWER on a text column results in: ERROR util.JDBCExceptionReporter - Argument data type text is invalid for argument 1 of upper function. http://databases.aspfaq.com/database/why-do-i-get-argument-data-type-text... suggests a workaround, which I think should be automatically used by Hibernate, so that the HQL query can work with other dialects. -- 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

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3965) Expose the ability to use varchar(max) or nvarchar(max)

by Ido Ran (JIRA)

Expose the ability to use varchar(max) or nvarchar(max) ------------------------------------------------------- Key: HHH-3965 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3965 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.4.0GA as provider for JPA 1.0 - SQL Server 2005 Database Reporter: Ido Ran Priority: Blocker I have an entity which needs to store long text field (at least 30,000 characters). I use SQL Server 2005 as back-end database. SQL Server varchar support up-to 8,000 characters in length of a field, or the reserved word MAX which indicate that the field length will be 2^31-1. I think that the class SQLServerDialect should be changed to have the following line in it's ctor: registerColumnType( Types.VARCHAR, 8001, "varchar(MAX)" ); this way, all String fields with length above 8000 will have varchar(MAX) as column 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, 10 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-517) ThreadLocal in ContextHolder causes memory leak when deployed in a web container

by Vojtěch Krása (JIRA)

ThreadLocal in ContextHolder causes memory leak when deployed in a web container -------------------------------------------------------------------------------- Key: HSEARCH-517 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-517 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.CR1, 3.2.0.Beta1, 3.1.1.GA, 3.1.0.GA, 3.1.0.CR1, 3.1.0.Beta2, 3.1.0.Beta1, 3.0.1.GA, 3.0.0.GA Environment: Hibernate 3.4.0.GA/3.5.1-Final, Tomcat 6.0.26, Spring 2.5.6/3.0.1, Sun JDK 1.6; Hibernate 3.3.1.GA Tomcat 6.0.18 Spring 2.5.6 Java OpenJDK 1.6 Reporter: Vojtěch Krása Priority: Critical Attachments: dump.zip, testCase.zip The SearchFactory has a static ThreadLocal variables which holds a reference to the SearchFactoryImpl. The ThreadLocal is not cleared when the application is undeployed, causing a memory leak. http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-314 -- 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
8
0 / 0

[Hibernate-JIRA] Created: (METAGEN-44) getting Runtime error message "o.h.e.m.MetadataContext - Unable to locate static metamodel field"

by Young Lee (JIRA)

getting Runtime error message "o.h.e.m.MetadataContext - Unable to locate static metamodel field" ------------------------------------------------------------------------------------------------- Key: METAGEN-44 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-44 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.1.0.CR1 Reporter: Young Lee Assignee: Hardy Ferentschik Attachments: test.jar I have a @MappedSuperClass declared as @MappedSuperClass public abstract class IdentifiableComponent<T extends EmbeddableId> extends RecordTimestamp2 implements Serializable and my Entity class declared as @Entity public class AppRegistration extends IdentifiableComponent<AppRegistrationId> and the Composite Id class declared as @Embeddable public class AppRegistrationId implements EmbeddableId The metamodel is generated properly, but at runtime I get the following error message o.h.e.m.MetadataContext - Unable to locate static metamodel field : com.playspan.lookup.model.AppRegistration_#id I've tried adding @IdClass(AppRegistrationId) annotation to the AppRegistration Entity class, but still I get the same error message. Please tell me what I am doing wrong. Thanx in advance. Attached is a complete sample buildable maven project with the above classes -- 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
4
0 / 0

[Hibernate-JIRA] Created: (BVTCK-12) The TCK goes against the spec on Node and nested Path: section 4.2

by Emmanuel Bernard (JIRA)

The TCK goes against the spec on Node and nested Path: section 4.2 ------------------------------------------------------------------ Key: BVTCK-12 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVTCK-12 Project: Bean Validation TCK Issue Type: Bug Affects Versions: 1.0.4.GA Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Priority: Minor In section 4.2 "Constraint Violation", Table 4.1, "propertyPath examples", the structure of a set of Path.Nodes is described. Examining the examples in this section: Row 4 shows that a path describing the fourth author (i.e. "authors3") should be represented by a not-in-iterable "authors" node followed by a nameless node with index 3. However, in this example the TCK would expect a single "authors" node with index 3. Likewise, row 6 shows that a path describing the first author's company property ("authors0.company") should be represented by a not-in-iterable "authors" node followed by a "company" node with index 0. In this example the TCK would instead expect an "authors" node with index 3, followed by a not-in-iterable "company" node. -- 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

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5403) Update to hsqldb 2.0.0 for testing

by Gail Badner (JIRA)

Update to hsqldb 2.0.0 for testing ---------------------------------- Key: HHH-5403 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5403 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Fix For: 3.5.x, 3.6.x When 2.0.0 is available from the JBoss Nexus repo, parent/pom.xml should be updated in Branch_3_5 and trunk so testing is done using 2.0.0. -- 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

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5492) PostInsertListener doing new insert works on Mysql/HSQLDB, but not on Oracle.

by Barry (JIRA)

PostInsertListener doing new insert works on Mysql/HSQLDB, but not on Oracle. ----------------------------------------------------------------------------- Key: HHH-5492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5492 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.4 Environment: Oracle Database 10g Express Edition Release 10.2.0.1.0 and Oracle Database 11g Release 11.1.0.0.0 Reporter: Barry Attachments: EventListener-test.zip I'm trying to implement a hibernate event listener that inserts a new record every time a specific entity is updated, deleted or inserted. I've implemented a listener for post-insert, post-update, post-delete. Its a requirement that the new record is inserted in the same transaction as the one that originally triggered the update/deletion/insert. The relevant section of my listener looks like this (similar for postInsert & postDelete): {code} public void onPostUpdate(PostUpdateEvent event) { if (isAuditable(event.getEntity())) { saveAuditRecord(event.getSession()); } } private boolean isAuditable(Object entity) { return entity instanceof SomeEntity; } private void saveAuditRecord(Session session) { AuditRecord record = new AuditRecord(); record.setId(Double.doubleToLongBits(Math.random())); session.save(record); } {code} The listener is triggered for each event, but it seems as though the AuditRecord is not saved when using an Oracle database. Using MySQL or HSQLDB works fine. So my guess is that it has something to do with the Oracle dialect? I've attached a test case which demonstrates it failing (but you will need to connect to an Oracle DB :-)) Same result for Oracle XE and the full monty. -- 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

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2010