September 2010 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-5297) Hibernate JPA closes XAConnection on Glassfish v3 with JDBC Wrapping

by Radosław Smogura (JIRA)

Hibernate JPA closes XAConnection on Glassfish v3 with JDBC Wrapping -------------------------------------------------------------------- Key: HHH-5297 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5297 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Environment: Glassfish v 3 Reporter: Radosław Smogura Priority: Critical In EJB application at 90% the Hibernate closes original physicall connectiont o XA database. This problem occurs when JDBC Object wrapping is turned on in Glassfiah admin console. This bug is "upstream" of this https://glassfish.dev.java.net/issues/show_bug.cgi?id=11846. Orginal initial comment, and some comments: ---------------------- I use PostgreSQL 8.4 with trunk and stable driver. When I use statement caching with wrapping original objects I got exception that statement is closed. My investigation shwn close of original Polled Connection in com.sun.gjc.spi.ManagedConnection.transactionCompleted. Problem disappears after few calls of same statement. This problem doesn't occurs when wrapping is turned off. In both cases I use XA poll. Caused by: org.postgresql.util.PSQLException: Statement has been closed. at org.postgresql.ds.jdbc23.AbstractJdbc23PooledConnection$StatementHandler.invoke(AbstractJdbc23PooledConnection.java:448) at $Proxy227.clearParameters(Unknown Source) at com.sun.gjc.spi.base.PreparedStatementWrapper.clearParameters(PreparedStatementWrapper.java:380) at com.sun.gjc.spi.base.PreparedStatementWrapper.close(PreparedStatementWrapper.java:755) at org.hibernate.jdbc.AbstractBatcher.closePreparedStatement(AbstractBatcher.java:563) ----------------- This problem isn't visible if PooligDatasource is used. ----------------- I used 3.5.2 Release and it's looks same. Before 1st submiting bug I thought that this is GF problem, becasue in EJB I was trying to get XAConnection by resource injection and same problem occured (this EJB was mixed Hibernate + JDBC), but now i'm going to point that this is Hibernate problem. I'll do some other checks, and if this will be Hibernate problem I'll fill bug in Hib. I created application without Hibernate (old plain JNDI) and it looks that there is no error - so this coud be hibernate. But i want to do more test, about this (eg. take XAConnection from server global JNDI, without java:comp/env). ----------------- --- Kind regards, Radosław Smogura http://www.softperience.eu -- 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
6
0 / 0

[Hibernate-JIRA] Created: (EJB-385) JPA method of merge failed to insert deleted records from database

by Hari (JIRA)

JPA method of merge failed to insert deleted records from database ------------------------------------------------------------------- Key: EJB-385 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-385 Project: Hibernate Entity Manager Issue Type: Improvement Components: EntityManager Affects Versions: 3.2.0.ga Environment: 3.2.6.ga, Weblogic,JPA, Windows Reporter: Hari The following is my requirement. Suppose i have a record in database with id say, 12. i have retrieved this using a JPQL query and convert it into a transfer object ,done some processing and going to remerge this after converting it to a new entity but the id set in the new entity is same as old one ie 12. Now just before calling entityManger.merge i have deleted the record with id 12 from database. The issue is the merge opeartion is not inserting the record in database at all. But if the id set in the entity is one which is never occured in the database,the merge operation will insert the record with the id set from teh application. Is there any work around/fix for this issue. Regards Harikrishnan R -- 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: (ANN-853) Implement JPA 2.0 annotation support

by Emmanuel Bernard (JIRA)

Implement JPA 2.0 annotation support ------------------------------------ Key: ANN-853 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-853 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Emmanuel Bernard Fix For: 3.5 -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4066) JPA compatibility problem

by Albert Kurucz (JIRA)

JPA compatibility problem ------------------------- Key: HHH-4066 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4066 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2 Environment: Hibernate Core 3.3.2, problem is independent from database type (actually appeared with Derby 10.4.2) Reporter: Albert Kurucz POJO Entity with 100% JPA annotations, as long as the Class did not implement the Map interface everything worked fine (save to and load from database). After the Class implemented the Map interface, during object persistence, 'get' was called with '$type$' parameter, and 'get' responded with IllegalArgumentException (in accordance to its design). Workaround implemented: get now responds to this call by returning getClass().getName() BUT Hibernate should not need this workaround if it is 100% JPA compliant. On the above example the Map interface of the Entity Class had no connection with persisted variables, only transients. In the JPA spec there is no restriction what I know of, which would disallow the implementation of Map by an Entity Class. In the JPA spec there is no requirement what I know of, which would require and Entity Class which implement the Map interface to implement the Map interface in any special way (like 'get' responding to '$type$'). Correct me if I am wrong. -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3223) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

by Michael Newcomb (JIRA)

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-3223 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3223 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.CR1 Reporter: Michael Newcomb Please have a look at PersistentMap.remove() and compare it to PersistentMap.put(). The put() was fixed HHH-2476 and the same fix needs to be applied to remove(). Please refer to HHH-2584 for the patch: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Copied from HHH-2584: Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly. WORKAROUND: Have a copy of PersistentMap.java in your source tree with the patch applied... Thanks! -- 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

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3459) NullPointerException in Formatter.isFunctionName with certain SQL when pretty format is used

by Scott Feldstein (JIRA)

NullPointerException in Formatter.isFunctionName with certain SQL when pretty format is used -------------------------------------------------------------------------------------------- Key: HHH-3459 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3459 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.6 Reporter: Scott Feldstein A NullPointerException is thrown when hibernate.show_sql=true && hibernate.format_sql=true while exec'ing sql with quotes around the stmt: (taken from an embedded groovy script) --------- def sess = getSession() def HQL = """ (select count(*) from TABLE) """ sess .createSQLQuery(HQL) .list() ------------ This is valid SQL and is typically used in my app as such: (select count(*) from TABLE1) UNION ALL (select count(*) from TABLE2) ... Here is the stack trace in hibernate: java.lang.NullPointerException at org.hibernate.pretty.Formatter.isFunctionName(Formatter.java:342) at org.hibernate.pretty.Formatter.openParen(Formatter.java:323) at org.hibernate.pretty.Formatter.format(Formatter.java:134) at org.hibernate.jdbc.AbstractBatcher.format(AbstractBatcher.java:410) at org.hibernate.jdbc.AbstractBatcher.log(AbstractBatcher.java:404) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:482) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:423) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547) at org.hibernate.loader.Loader.doQuery(Loader.java:673) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2220) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:289) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1695) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:152) -- 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
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

14 years, 8 months

3
2
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

14 years, 8 months

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

14 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-364) Composite PK and @GeneratedValue

by Radosław Smogura (JIRA)

Composite PK and @GeneratedValue -------------------------------- Key: EJB-364 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-364 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.2.GA Environment: Hibernate 3.2.6 Glassfish PostgreSQL Reporter: Radosław Smogura Priority: Critical [code] For class like this @Entity @IdClass(FooId.class) /* Seq / Table generator */ public class Foo { int id1; int id2; @Id public getId1() { return id1; } public setId1(....); @Id @GeneratedValue(strategy=AUTO/IDENTITY/SEQUENCE/TABLE) public int getId2() { return id2; } public void setId2(.....); } [/code] Id1 is set manully, but id2 is unchanged i this situation hibernate doesn't generates PK and tries to insert NULL causing error. Specification requires assigning of generated value with @Id properties. Part 2.4.1 defines two types of PKs simple and composite and part 9.1.9 says about PKs in generally. (SEQ or IDENTITY is specification depended, but PostgreSQL support it and Hibernate should support it too). -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2010