June 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-679) Entity whose related entity collection is updated causes loading of @ContainedIn entities

by Tom Waterhouse (JIRA)

Entity whose related entity collection is updated causes loading of @ContainedIn entities ----------------------------------------------------------------------------------------- Key: HSEARCH-679 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-679 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.1, 3.4.0 Environment: Hibernate 3.6.1-SNAPSHOT/Hibernate Search 3.4.0-SNAPSHOT and Hibernate 3.5.6/Hibernate Search 3.2.1 Reporter: Tom Waterhouse This problem seems related to HSEARCH-361. An entity that references another entity as @ContainedIn is causing the load of entities related to the other entity. Using the model below, the update of the collection of D instances in the class C causes the load of related classes B and A. public class A { @Field private String name; @IndexEmbedded private B } public class B { @ContainedIn private A a; @IndexEmbedded private C c; } public class C { @ContainedIn private Collection<B> b; // NOT INDEXED private Collection<D> d; } public class D { public String 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

13 years

7
30
0 / 0

[Hibernate-JIRA] Created: (HHH-3495) CollectionAction instances can consume considerable memory in large transactions unnecessarily

by Tim Downey (JIRA)

CollectionAction instances can consume considerable memory in large transactions unnecessarily ---------------------------------------------------------------------------------------------- Key: HHH-3495 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3495 Project: Hibernate Core Issue Type: Improvement Reporter: Tim Downey Attachments: CollectionActionPatch.zip Hi, We're doing some fairly heavy duty batch processing using Hibernate 3.3.1. In doing so, we're basically paging over large chunks of entities where we flush and clear the session around pages. We do not commit between pages. We may be processing hundreds of thousands of entities over pages of ten to twenty thousand each. We're clearing the session around pages in attempt to free up memory that is no longer necessary. We have found that subtypes of CollectionAction get added to a list of Executable in the ActionQueue when there are collection changes processed. These CollectionActions are held until transaction complete and are not released on flush or clear of the session. Furthermore, the CollectionAction instances hold references to those collections that have changed even after the entities have been evicted from the session. In our case, this was causing Hibernation to hold on to several hundred MB of RAM until transaction commit. I've supplied a small patch that doesn't require the CollectionAction to hang on to the entities themselves until the transaction boundary. We're showing considerably improvement in memory utilization as a result. I'm hoping that you consider this patch for inclusion in a future release. The change was basically to change the ActionQueue's list of Executables used in after transaction completion, to a separate type, AfterTransactionCompletionExecutable. This new type allows some decoupling in the other subclasses of Executable to hold references to fewer resources and save considerable memory when the transaction sizes are quite large. Regards, Tim -- 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

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2169) L2 Cache and Long transactions Memory Leak : OutOfMemoryException

by Sami Dalouche (JIRA)

L2 Cache and Long transactions Memory Leak : OutOfMemoryException ----------------------------------------------------------------- Key: HHH-2169 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2169 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: [b]Hibernate version:[/b] Hibernate Entity Manager 3.2.0, with Hibernate Core 3.2.0 and Hibernate Annotations 3.2.0 [b]Mapping documents:[/b] Annotations [b]Full stack trace of any exception that occurs:[/b] Memory Heap Exception [b]Name and version of the database you are using:[/b] PosgreSQL 8.1 Reporter: Sami Dalouche Summary --------- When enabling L2 Cache (with either OScache and EhCache, both with a limitation on the max #of instances, so the problem shouldn't come from the cache manager), Hibernate cannot have long running transactions, otherwise, it results in a Memory Heap Exception... The problem does NOT happen if the L2 Cache is disabled ! Details ---------- - Configure the code to run in ONE transaction - Have a huge loop that inserts 2 million entries that are cacheable (@Cache(usage = CacheConcurrencyStrategy.NONSTRICT_READ_WRITE)) - flush() and clear() every 1000 entries, to periodically flush the cache => None of the entries are garbage collected. => Using a profiler, it is possible to trace the owning objects of my domain classes to : - org.hibernate.action.EntityInsertAction ("instance" variable) - array / List (variable elementData) - variable "executions" in object .. class org.hibernate.engine.ActionQueue Remarks : - If the Query Cache is disabled, and the objects being inserted are NOT cacheable (no @Cache annotation), there is no problem - If the Query Cache is enabled, then, no matter whether the objects being inserted are cacheable or not, The entries are never garbage collected, and I get an OutOfMemoryException. (I see NO relationship between the Query Cache and my objects. I never query the objects, only save them !!) -- 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

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3195) session.clear() is not effective when use_query_cache is true

by James Berry (JIRA)

session.clear() is not effective when use_query_cache is true ------------------------------------------------------------- Key: HHH-3195 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: 3.2.6.ga, MySQL5 Reporter: James Berry As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing many inserts while use_query_cache is enabled will eventually cause an out of memory condition, even if the session is periodically flushed and cleared. That forum thread describes a potential root cause for this problem. Nobody from the Hibernate team has responded regarding the forum thread, even though it's been alive for three years now! Note that an answer to "disable the query cache" is not a good solution to the problem, as we need the query cache elsewhere. If it were possible to disable the query cache for a particular session, that would be fine, but I see no way do that. -- 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

7
9
0 / 0

[Hibernate-JIRA] Created: (HHH-6329) Apparently inaccurate 'java.lang.UnsupportedOperationException: Illegal attempt to edit read only item' when using SQLQuery.executeUpdate

by Alex Hayward (JIRA)

Apparently inaccurate 'java.lang.UnsupportedOperationException: Illegal attempt to edit read only item' when using SQLQuery.executeUpdate ----------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6329 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6329 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Affects Versions: 3.6.5 Environment: Hibernate 3.6.5, PostgreSQL, OpenJDK 7.0.144, FreeBSD 8.2 Reporter: Alex Hayward The following code (and, indeed, anything similar using INSERT): SQLQuery createSequence = sess.createSQLQuery("CREATE SEQUENCE printOrder" + getId()); createSequence.executeUpdate(); results in an attempt to flush the entire L2 cache. This, in turn, results in: java.lang.UnsupportedOperationException: Illegal attempt to edit read only item at org.hibernate.cache.infinispan.entity.ReadOnlyAccess.lockRegion(ReadOnlyAccess.java:28) at org.hibernate.action.BulkOperationCleanupAction$EntityCleanup.<init>(BulkOperationCleanupAction.java:205) at org.hibernate.action.BulkOperationCleanupAction$EntityCleanup.<init>(BulkOperationCleanupAction.java:199) at org.hibernate.action.BulkOperationCleanupAction.<init>(BulkOperationCleanupAction.java:120) at org.hibernate.engine.query.NativeSQLQueryPlan.coordinateSharedCacheCleanup(NativeSQLQueryPlan.java:176) at org.hibernate.engine.query.NativeSQLQueryPlan.performExecuteUpdate(NativeSQLQueryPlan.java:189) at org.hibernate.impl.SessionImpl.executeNativeUpdate(SessionImpl.java:1310) at org.hibernate.impl.SQLQueryImpl.executeUpdate(SQLQueryImpl.java:396) at BoxOffice.BusinessObjects.PrintQueue.createPrintOrderSequence(PrintQueue.java:77) at BoxOffice.Server.CorbaImpl.PrintManager.addPrintQueue(PrintManager.java:808) at BoxOffice.Server.CorbaImpl.PrintManagerImpl.addPrintQueue(PrintManagerImpl.java:938) at BoxOffice.CORBA.PrintManagerPOATie.addPrintQueue(PrintManagerPOATie.java:78) at BoxOffice.CORBA.PrintManagerPOA._invoke(PrintManagerPOA.java:198) at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:301) at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:604) at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:747) 'persister' on line 120 of BulkOperationCleanupAction is 'SingleTableEntityPersister(BoxOffice.BusinessObjects.Country)' when this happens. 'Country' is a read-only object. None have been modified. Using doWork instead works, but is unfortunately a rather awkward API for many cases. -- 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
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6327) NPE when using JDBC connection pool C3pO

by Guenther Demetz (JIRA)

NPE when using JDBC connection pool C3pO ---------------------------------------- Key: HHH-6327 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6327 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.Beta1 Environment: Hibernate4beta1 Reporter: Guenther Demetz org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.java (hibernate-c3p0-3.6.0.Beta1-sources.jar) does not implement interface org.hibernate.service.spi.Configurable so the method configure is never called, this leads to a NPE while building the SessionFactory. Please see https://forum.hibernate.org/viewtopic.php?f=1&t=1011445 for more details. -- 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

2
3
0 / 0

[Hibernate-JIRA] Created: (JPA-16) duplicated id column when abstract id methods are defined in a @MappedSuperclass

by Constantino Cronemberger (JIRA)

duplicated id column when abstract id methods are defined in a @MappedSuperclass -------------------------------------------------------------------------------- Key: JPA-16 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-16 Project: Java Persistence API Issue Type: Bug Environment: Database H2, Hibernate 3.6.4.Final Reporter: Constantino Cronemberger Priority: Minor The following classes: @MappedSuperclass public abstract class BaseEntity { public abstract Long getId(); public abstract void setId(Long id); } @Entity @Table(name="STCB") public class SimpleTestClassB extends BaseEntity { private Long primaryKey; @Override @Id @Column(nullable = false, precision = 10, name = "sb_id") public Long getId() { return primaryKey; } @Override public void setId(Long primaryKey) { this.primaryKey = primaryKey; } } will generate the following table: create table STCB (sb_id number(19,0) not null, id number(19,0), primary key (sb_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

13 years

1
1
0 / 0

[Hibernate-JIRA] Created: (OGM-50) Write simple reference documentation

by Emmanuel Bernard (JIRA)

Write simple reference documentation ------------------------------------ Key: OGM-50 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-50 Project: Hibernate OGM Issue Type: New Feature Components: documentation Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 1.0-next -- 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
1
0 / 0

[Hibernate-JIRA] Created: (OGM-76) Upgrade various dependency versions

by Emmanuel Bernard (JIRA)

Upgrade various dependency versions ----------------------------------- Key: OGM-76 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-76 Project: Hibernate OGM Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Priority: Minor Infinispan to 5 CR5 hibernate-JPA to 1.0.1 Shrinkwrap to 1 beta2 JBoss transaction to 4.15.1 -- 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
1
0 / 0

[Hibernate-JIRA] Created: (HV-315) Create package-level JavaDoc for the AP

by Gunnar Morling (JIRA)

Create package-level JavaDoc for the AP --------------------------------------- Key: HV-315 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-315 Project: Hibernate Validator Issue Type: Improvement Components: annotation-processor Affects Versions: 4.1.0.Beta1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik Priority: Minor Fix For: 4.1.0 Currently there are no package-level JavaDocs for the AP. These should be added. The top-level doc should contain an overview over the APs architecture in general. -- 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

4
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