June 2011 - hibernate-issues - Jboss List Archives

[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

13 years, 1 month

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

13 years, 1 month

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

13 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6006) orm_2_0.xsd doesn't match JPA 2.0 spec for order-column

by David Carr (JIRA)

orm_2_0.xsd doesn't match JPA 2.0 spec for order-column ------------------------------------------------------- Key: HHH-6006 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6006 Project: Hibernate Core Issue Type: Bug Components: core Reporter: David Carr In the JPA 2.0 spec, in section 12.3 (XML Schema), for the "order-column" type, it has an attribute: <xsd:attribute name="table" type="xsd:string"/> This attribute appears to be missing from orm_2_0.xsd. -- 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-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

13 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HV-503) cann't format some special sql in sometimes

by xu (JIRA)

cann't format some special sql in sometimes ------------------------------------------- Key: HV-503 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-503 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta2 Environment: jdk 5, windows xp Reporter: xu Attachments: test.rar when I use BasicFormatterImpl to format some special sql, a exception will be throw.And the sql is certainly right. It can be query in our database.The class I'm using is BasicFormatterImpl.And I format the sql like this: System.out.println(new BasicFormatterImpl().format(str)); The testcase is in the attachment.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

13 years, 1 month

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

13 years, 1 month

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

13 years, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5884) Negation of CompoundPredicate (JPA 2.0 Criteria API) does not create SQL with negated predicate.

by Aleksandras Novikovas (JIRA)

Negation of CompoundPredicate (JPA 2.0 Criteria API) does not create SQL with negated predicate. ------------------------------------------------------------------------------------------------ Key: HHH-5884 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5884 Project: Hibernate Core Issue Type: Bug Environment: hibernate-distribution-3.6.0.Final Reporter: Aleksandras Novikovas Priority: Blocker Attachments: Main.java, persistence.xml, TestEntity.java Negating of CompoundPredicate (conjunction or disjunction) does not create negated SQL. [https://forum.hibernate.org/viewtopic.php?f=1&t=1008886] With this bug Hibernate does not comply to JSR317 specification. -- 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: (HSEARCH-626) Allow MassIndexer to work in parallel of regular indexing / querying

by Emmanuel Bernard (JIRA)

Allow MassIndexer to work in parallel of regular indexing / querying -------------------------------------------------------------------- Key: HSEARCH-626 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-626 Project: Hibernate Search Issue Type: New Feature Components: massindexer Reporter: Emmanuel Bernard Some people want to use mass indexer to reindex live some data. This is problematic today as MassIndexer expects to work alone / offline. I can see at least one approach: - copy the index to a new Directory before mass indexing (or if exclusive, start with a new Directory while keeping the old Directory in place - the current directory needs to become read-only - all index update (on the entity) requests should be queued up for after massIndexer is done - MassIndexer swaps the current and the new directory - indexing and querying resume as normal Note that we need to work on a different directory because mass indexer does delete all entries of an entity before starting the reindexing process. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2011