October 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-1989) Deleted object remains referenced in 2nd level cache collections

by Justin Haddad (JIRA)

Deleted object remains referenced in 2nd level cache collections ---------------------------------------------------------------- Key: HHH-1989 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1989 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: Spring 1.2.8, Hibernate 3.2, Postgres 8.0.3 Reporter: Justin Haddad This problem seems identical to issue NH-678. I have enabled caching for an one-to-many association. I use Ehcache. I have a test in which I load the parent object along with its collection. Both the parent and the collection wind up in the 2nd level cache. I then delete an object that is in the collection, not by removing it from the collection, but rather by doing a delete on the object itself. After deleting, I try to reload the parent and get the following exception (User#3102 is the deleted object): aused by: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.bluenotenetworks.common.management.sm.User#3102] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:372) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:128) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:839) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) at org.hibernate.collection.PersistentSet.initializeFromCache(PersistentSet.java:101) at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1705) (continues on) I stepped through the code in the debugger and can see that the object's ID (3102 in this case) remains in the cached collection even after the deletion. -- 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, 10 months

3
2
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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-1992) Some cascade actions should not trigger a property access on lazy properties

by Emmanuel Bernard (JIRA)

Some cascade actions should not trigger a property access on lazy properties ---------------------------------------------------------------------------- Key: HHH-1992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1992 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr3 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Critical Fix For: 3.2.0.ga -- 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, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2088) TypeMismatchException on object equality expression from one-to-one relationship

by Salvatore Insalaco (JIRA)

TypeMismatchException on object equality expression from one-to-one relationship -------------------------------------------------------------------------------- Key: HHH-2088 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2088 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Reporter: Salvatore Insalaco Suppose to have entity A with a one-to-one constrained relationship to an entity B, called bRel. The query: "from A a, B b where a.bRel = b" raises a TypeMismatchException, even if bRel and b are instances of the same entity. This happens because in BinaryLogicOperatorNode: - lhsType is org.hibernate.type.Type = org.hibernate.type.OneToOneType(B)", with getColumnSpan returning 0. - rhsType is org.hibernate.type.Type = org.hibernate.type.ManyToOneType(B)", with getColumnSpan returning 1. And it compares the two columnspans. It doesn't happen with 3.2.0.cr2. -- 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

15 years

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2047) make Query and Criteria extend java.lang.Iterable

by Amir Pashazadeh (JIRA)

make Query and Criteria extend java.lang.Iterable ------------------------------------------------- Key: HHH-2047 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2047 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.cr2 Reporter: Amir Pashazadeh Priority: Trivial Objects which implement java.lang.Iterable can be iterated using extended for 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

15 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-407) <synchronize table="table_name"/> is missed using annotations

by Amir Pashazadeh (JIRA)

<synchronize table="table_name"/> is missed using annotations -------------------------------------------------------------- Key: ANN-407 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-407 Project: Hibernate Annotations Type: Patch Components: binder Versions: 3.2.0.cr1 Reporter: Amir Pashazadeh in old .hbm.xml notation there was a possibility to set a synchronize for caches on particular tables, and I could not find such thing using annotations, is it possible to set "synchronize" tables using annotations? and if not will it be added to 3.2? -- 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

15 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-1985) NodeTraverser is not SOE-safe

by Sergey Vladimirov (JIRA)

NodeTraverser is not SOE-safe ----------------------------- Key: HHH-1985 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1985 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.cr3 Reporter: Sergey Vladimirov Priority: Minor org.hibernate.hql.ast.util.NodeTraverser It is possible for java.lang.StackOverflowError to occur in NodeTraverser.java:41;42 with very deep tree. Need another algorith to visit whole tree. 08.08 19:50:09 ERROR [ArpSiteServlet] Servlet.service() for servlet ArpSiteServlet threw exception java.lang.StackOverflowError at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:41) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:41) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) -- 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

15 years, 2 months

7
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2094) Hibernate is ignoring native sql aliases and generating "column not found" error

by Leonardo Penczek (JIRA)

Hibernate is ignoring native sql aliases and generating "column not found" error -------------------------------------------------------------------------------- Key: HHH-2094 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2094 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.2.0.cr4 Environment: 3.2.0.cr4, Adaptive Server Enterprise/12.5.3 Reporter: Leonardo Penczek Priority: Critical As simples as that: 1: Query q = em.createNativeQuery("select cd_person as codePerson, cd_person as identif from PERSON"); 2: List<Object[]> resultList = (List<Object[]>) q.getResultList(); Hibernate is ignoring my aliases when retrieving information from the ResultSet because it is trying to retrieve by column name, generating the following error: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:641) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:73) at <my line 2 in the code above> ... Caused by: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2147) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2028) at org.hibernate.loader.Loader.list(Loader.java:2023) 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:150) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:64) ... Caused by: java.sql.SQLException: S0022: Invalid column name 'cd_person'. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source) at com.sybase.jdbc3.tds.TdsResultSet.findColumnByLabel(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.findColumn(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getInt(Unknown Source) at org.jboss.resource.adapter.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:690) at org.hibernate.type.IntegerType.get(IntegerType.java:28) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:113) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:139) at org.hibernate.loader.custom.CustomLoader$ScalarResultColumnProcessor.extract(CustomLoader.java:474) at org.hibernate.loader.custom.CustomLoader$ResultRowProcessor.buildResultRow(CustomLoader.java:420) at org.hibernate.loader.custom.CustomLoader.getResultColumnOrRow(CustomLoader.java:317) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:594) at org.hibernate.loader.Loader.doQuery(Loader.java:689) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2144) Awesome! The SQL query runs, but the Hibernate try to get the column by the original name, not by the alias, causing the error! It is not possible to correctly get the value of 2 different columns that have the same name!!!! Hint: why Hibernate use ResultSet.get* by column name instead of positional ResultSet.get* (1, 2, 3,...)? It will solve this 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

15 years, 3 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2146) NullpointerException in DefaultDeleteEventListener.deleteTransientEntity

by Martin Kartumovich (JIRA)

NullpointerException in DefaultDeleteEventListener.deleteTransientEntity ------------------------------------------------------------------------ Key: HHH-2146 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2146 Project: Hibernate3 Type: Bug Versions: 3.2.0.cr5 Environment: Hibernate 3.2.0cr5, Oracle10g Reporter: Martin Kartumovich Priority: Blocker The following setup leads to a NPE in DefaultDeleteEventListener.deleteTransientEntity: Tables A, B Table V_A_B that is an M-N-Connection between A and B. Pojo for A has a Set of V_A_Bs. Pojo for B has a Set of V_A_Bs. Pojo C that has Sets of As and Bs. Cascades: all, delete-orphan -Create a new A and add a new V_A_B to its Set, that references to an existing B. -Delete B. -SaveOrUpdate Pojo C. In Hibernate 3.1.3 this works fine. In 3.2.0cr4+cr5 the removal of B results into an cascading removal of the never persisted V_A_B in the Set of B instead of ignoring it. This leads to an incorrect state where deleteTransientEntity is called with transientEnties=null. When now calling transientEnties.contains(...) the NPE is thrown. -- 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

15 years, 3 months

22
33
0 / 0

[Hibernate-JIRA] Created: (HHH-2142) PersistentMap.put(), remove() may return UNKNOWN object that can cause ClassCastException in client code

by Andrzej Miazga (JIRA)

PersistentMap.put(), remove() may return UNKNOWN object that can cause ClassCastException in client code -------------------------------------------------------------------------------------------------------- Key: HHH-2142 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2142 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr5 Reporter: Andrzej Miazga Here is some code in Hibernate 3.2.0cr5 that may cause this behaviour. I'm not sure if this is a bug but it surely affects the client code. AbstractPersistentCollection: protected Object readElementByIndex(Object index) { if (!initialized) { ... return persister.getElementByIndex( entry.getLoadedKey(), index, session, owner ); } ... return UNKNOWN; } PersistentMap (extends AbstractPersistentCollection): public Object put(Object key, Object value) { if ( isPutQueueEnabled() ) { Object old = readElementByIndex( key ); queueOperation( new Put( key, value, old ) ); return old; } ... So, there is a possibility to return UNKNOWN instance (MarkerObject) to the client code as the result of Map.put(). In version 3.1.3 this worked fine, but the implementation was different: public Object put(Object key, Object value) { Object old = isPutQueueEnabled() ? readElementByIndex(key) : UNKNOWN; if ( old==UNKNOWN ) { write(); return map.put(key, value); } ... } -- 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

15 years, 5 months

9
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2006