June 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-762) enabled exclusive_index_use=true by default

by Sanne Grinovero (JIRA)

enabled exclusive_index_use=true by default ------------------------------------------- Key: HSEARCH-762 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-762 Project: Hibernate Search Issue Type: Improvement Components: documentation, engine Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha1 great performance improvement, while this was the recommended configuration it wasn't enabled by default for backwards compatibility. -- 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, 1 month

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6322) upgrade to hibernate-jpa-2.0-api-1.0.1.Final

by Strong Liu (JIRA)

upgrade to hibernate-jpa-2.0-api-1.0.1.Final -------------------------------------------- Key: HHH-6322 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6322 Project: Hibernate Core Issue Type: Task Components: build Reporter: Strong Liu Assignee: Strong Liu -- 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, 1 month

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6370) HSQLDB dialect - fixes reported issues and adds minor enhancement

by Fred Toussi (JIRA)

HSQLDB dialect - fixes reported issues and adds minor enhancement ----------------------------------------------------------------- Key: HHH-6370 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6370 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.6.5, 3.5.6 Environment: Hibernate 3.6.x, HSQLDB 1.8.x and 2.x.x Reporter: Fred Toussi Attachments: HSQLDialect.patch Corrections - fixes HHH-5503 - second(datetime) function requires cast to integer as with HSQLDB 2.x.x it can return BigDecimal to include second fractions. - nulls in SELECT lists are now supported for BLOB and other previously missing types. - COMMENT ON is supported only in 2.x.x Enhancements - fixes HHH-6012 - added a few common function 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

13 years, 1 month

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5503) HSQLDialect uses invalid select-clause null string for BLOB on HSQLDB 2.0

by Bart Bakker (JIRA)

HSQLDialect uses invalid select-clause null string for BLOB on HSQLDB 2.0 ------------------------------------------------------------------------- Key: HHH-5503 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5503 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.5.5, 3.5.4 Environment: HSQLDB 2.0 Reporter: Bart Bakker The union select statement that is generated for multiple subclasses of an entity, when one of the subclasses uses a Lob, contains an invalid cast null on HSQLDB 2.0. >From version 2.0 on HSQLDB supports data type BLOB and no longer forces using longvarbinary for blobs. While the HSQLDialect registers the appropriate column type for LOB now, it uses "cast(null as int)" in its getSelectClauseNullString in the union select described above, which causes HSQLDB error 'incompatible data types in combination'. -- 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, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6178) Mapping bidirectional one-to-one relationship fails with an AnnotationException: Unknown mappedBy in: / referenced property unknown

by Karsten Wutzke (JIRA)

Mapping bidirectional one-to-one relationship fails with an AnnotationException: Unknown mappedBy in: / referenced property unknown ----------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6178 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6178 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Environment: Hibernate 3.6.0 Final, HSQLDB 2.0.1 RC, JavaSE Reporter: Karsten Wutzke Priority: Critical Mapping a simple bidirectional one-to-one relationship fails with an AnnotationException for no obvious reason. DB design: CREATE TABLE Persons ( id INTEGER NOT NULL, first_name VARCHAR(50) NOT NULL, last_name VARCHAR(50) NOT NULL, PRIMARY KEY (id) ); CREATE TABLE Coaches ( id INTEGER NOT NULL, license_nbr VARCHAR(10) DEFAULT NULL NULL, PRIMARY KEY (id), FOREIGN KEY (id) REFERENCES Persons (id) ); CREATE TABLE Players ( id INTEGER NOT NULL, registration_nbr VARCHAR(20) DEFAULT NULL NULL, PRIMARY KEY (id), FOREIGN KEY (id) REFERENCES Persons (id) ); Mappings (relevant shown only): @Entity @Table(name = "Persons") public class Person implements Serializable { @Id @Column(name = "id") private Integer id; @Column(name = "first_name") private String firstName; @Column(name = "last_name") private String lastName; @OneToOne(mappedBy = "person") private Coach coach = null; @OneToOne(mappedBy = "person") private Player player = null; ... } @Entity @Table(name = "Players") public class Player implements Serializable { @Column(name = "registration_nbr") private String registrationNbr = null; @Id @OneToOne @JoinColumn(name = "id") private Person person = null; ... } @Entity @Table(name = "Coaches") public class Coach implements Serializable { @Column(name = "license_nbr") private String licenseNbr = null; @Id @OneToOne @JoinColumn(name = "id") private Person person = null; ... } The exception thrown in a test app: Exception in thread "main" javax.persistence.PersistenceException: [PersistenceUnit: persons] Unable to configure EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:374) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:56) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:48) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:32) at tld.persons.Main.main(Main.java:34) Caused by: org.hibernate.AnnotationException: Unknown mappedBy in: tld.persons.model.Person.coach, referenced property unknown: tld.persons.model.Coach.person at org.hibernate.cfg.OneToOneSecondPass.doSecondPass(OneToOneSecondPass.java:159) at org.hibernate.cfg.Configuration.originalSecondPassCompile(Configuration.java:1686) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1393) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1345) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1477) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:193) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:1096) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:278) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:362) ... 4 more This exception is really surprising given the simplicity of this design. I've also tested this with EclipseLink which has no problems with the mappings. I'll attach an test case including the full code. -- 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, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6296) Unnecessary lock in UpdateTimestampsCache

by Alexandre Thiel (JIRA)

Unnecessary lock in UpdateTimestampsCache ----------------------------------------- Key: HHH-6296 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6296 Project: Hibernate Core Issue Type: Patch Components: caching (L2) Affects Versions: 3.6.4, 3.6.3, 3.6.2, 3.6.1 Environment: Hibernate 3.6.4 Reporter: Alexandre Thiel Priority: Minor Attachments: UpdateTimestampsCache.java.diff Non transactional queries call UpdateTimestmapsCache.invalidate method with an empty array parameter but still acquire a WriteLock which cause a performance bottle neck under heavy load. GNU-Diff Patch for org.hibernate.cache.UpdateTimestampsCache attached Thread dump example : "TP-Processor10" daemon prio=10 tid=0x00000000415cb800 nid=0x6803 waiting on condition [0x00007f1346594000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00007f1370f6d1c0> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:778) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1114) at java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:807) at org.hibernate.cache.UpdateTimestampsCache.invalidate(UpdateTimestampsCache.java:88) at org.hibernate.engine.ActionQueue$AfterTransactionCompletionProcessQueue.afterTransactionCompletion(ActionQueue.java:604) at org.hibernate.engine.ActionQueue.afterTransactionCompletion(ActionQueue.java:209) at org.hibernate.impl.SessionImpl.afterTransactionCompletion(SessionImpl.java:602) at org.hibernate.jdbc.JDBCContext.afterNontransactionalQuery(JDBCContext.java:292) at org.hibernate.impl.SessionImpl.afterOperation(SessionImpl.java:595) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:993) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:978) -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5857) SQLServer dialect for varbinary incorrect for 2008

by Steve Mactaggart (JIRA)

SQLServer dialect for varbinary incorrect for 2008 -------------------------------------------------- Key: HHH-5857 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5857 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Steve Mactaggart In SQLServer 2008 the IMAGE data type has been deprecated and replaced with VARBINARY(MAX) {quote} ntext, text, and image data types will be removed in a future version of Microsoft SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max), varchar(max), and varbinary(max) instead. For more information, see Using Large-Value Data Types. {quote} The current SQLServer2008Dialect has the mapping (inherirted from SQLServerDialect): {code} registerColumnType( Types.VARBINARY, "image" ); {code} This needs to be reverted to use VARBINARY. {code} registerColumnType( Types.VARBINARY, "varbinary" ); {code} The issue is identified when using hibernate.ddl.auto=validate, it shows an error such as: {quote} Wrong column type in Database.dbo.BINARY_OBJECT for column BYTES. Found: varbinary, expected: image {quote} for an annotated fields such as: {code} @Column(name = "BYTES", length = 100000, nullable = true) private byte[] bytes; {code} -- 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, 1 month

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4830) @PostLoad -> LazyInitializationException: illegal access to loading collection ond a @OneToMany with FetchType.EAGER

by Cédric Templie (JIRA)

@PostLoad -> LazyInitializationException: illegal access to loading collection ond a @OneToMany with FetchType.EAGER -------------------------------------------------------------------------------------------------------------------- Key: HHH-4830 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4830 Project: Hibernate Core Issue Type: Bug Reporter: Cédric Templie I faced this issue without using JBoss although I found it on JBoss JIRA: https://jira.jboss.org/jira/browse/JBAS-5474 As a result I really think that it is an hibernate issue. -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5421) Accessing collection on PostLoad event causes LazyInitializationException

by Stu White (JIRA)

Accessing collection on PostLoad event causes LazyInitializationException ------------------------------------------------------------------------- Key: HHH-5421 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5421 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.3 Environment: Hibernate-3.5.3-Final Oracle 11g Reporter: Stu White Attachments: hibernate-test.zip We've encountered a problem using the PostLoad event to access a OneToMany Collection. Attempting to access the Collection in the PostLoad event handler results in a LazyInitializationException being thrown by AbstractEntityManagerImpl. The stack trace is below: javax.persistence.PersistenceException: org.hibernate.LazyInitializationException: failed to lazily initialize a collection, no session or session was closed at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1235) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:631) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:585) I've attached a JUnit test case containing the classes and configuration. We're using Oracle 11g and Hibernate v3.5.3-Final, but the test case uses HSQLDB. If there is any further information I can provide to help diagnose this then please let me know. -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6070) This is a big bug in the project

by Amol Patankar (JIRA)

This is a big bug in the project -------------------------------- Key: HHH-6070 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6070 Project: Hibernate Core Issue Type: Bug Components: build Affects Versions: 3.6.2 Environment: DEV, QA & Prod Reporter: Amol Patankar There is a big bug in the code which goes into 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

13 years, 1 month

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2011