[Hibernate-JIRA] Created: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
2:40 p.m.
Collection is not associated with any session exception when doing an eager fetch on a
non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate3
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
12:41 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Gail Badner commented on HHH-2862:
----------------------------------
Please attach a runnable test case (i.e., Java, mappings).
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate3
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
2:28 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Lorenzo Resta commented on HHH-2862:
------------------------------------
I am also having the same issue here. I tracked down that for some reason two collections
had the same owner, resulting in creation of to persistent collections. The reason for
that was corrupt data in our database, however after a debugging session i noticed that
StatefulPersistenceContext only removes already existing collections from the List
collectionEntries, but not from the List nonlazyCollections, which then leads to this
exception during the call forceInitialization on the collection since the session was
previously unset.
This is our mapping:
<hibernate-mapping>
<class name="ch.deltaenergy.et3000.customermgmt.Customer"
table="RET_CUSTOMER_V" schema="ET3000"
lazy="false" optimistic-lock="version">
<cache usage="nonstrict-read-write" include="all"
region="Basicdata.read-write"/>
<id name="creationSeq" type="java.lang.Long"
unsaved-value="-1">
<column name="CREATION_SEQ" precision="22"
scale="0" />
<generator class="sequence">
<param name="sequence">SEQ_UNIVERSAL</param>
</generator>
</id>
<version
column="hib_version"
name="hibVersion"
type="long"
access="property"
generated="always"/>
<property name="seqPk" type="java.lang.Long"
generated="always" insert="false" update="false">
<column name="SEQ_PK" precision="22"
scale="0" />
</property>
<property name="validFrom" type="java.util.Date"
generated="always" insert="false" update="false">
<column name="VALID_FROM" length="7" />
</property>
<property name="validTo" type="java.util.Date"
generated="always" insert="false" update="false">
<column name="VALID_TO" length="7" />
</property>
<many-to-one name="status" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3000.customermgmt.CustomerStatus"
cascade="none"
fetch="select"
column="STATUS_ID"/>
<many-to-one name="mandator" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3k.basicdata.Mandator"
cascade="none"
fetch="select"
column="MANDATOR_ID"/>
<property name="dateCreated" type="java.util.Date"
generated="always" insert="false" update="false">
<column name="DATE_CREATED" length="7" />
</property>
<many-to-one name="userCreated" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3k.basicdata.User"
cascade="none"
fetch="select"
column="USER_CREATED_ID"/>
<property name="functionCreated"
type="java.lang.String">
<column name="FUNCTION_CREATED" length="30" />
</property>
<property name="dateModified" type="java.util.Date"
generated="always" insert="false" update="false">
<column name="DATE_MODIFIED" length="7" />
</property>
<many-to-one name="userModified" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3k.basicdata.User"
cascade="none"
fetch="select"
column="USER_MODIFIED_ID"/>
<property name="functionModified"
type="java.lang.String">
<column name="FUNCTION_MODIFIED" length="30" />
</property>
<property name="customerNo" type="java.lang.String">
<column name="CUSTOMER_NO" length="30" />
</property>
<many-to-one name="parentCustomer" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3000.customermgmt.Customer"
cascade="none"
fetch="select"
column="PARENT_CUSTOMER_ID"/>
<property name="isCompany" type="yes_no">
<column name="IS_COMPANY_YN" length="1" />
</property>
<many-to-one name="customerType" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3000.customermgmt.CustomerType"
cascade="none"
fetch="select"
column="CUSTOMER_TYPE_ID"/>
<many-to-one name="language" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3k.translation.Sprache"
cascade="none"
fetch="select"
column="ISO_LANGUAGE_CD"/>
<property name="companyName" type="java.lang.String">
<column name="COMPANY_NAME" length="70" />
</property>
<property name="companyNameExt"
type="java.lang.String">
<column name="COMPANY_NAME_EXT" length="35" />
</property>
<property name="corporateStructure"
type="java.lang.String">
<column name="CORPORATE_STRUCTURE" length="20" />
</property>
<property name="holidayGroupId" type="java.lang.Long">
<column name="HOLIDAY_GROUP_ID" precision="22"
scale="0" />
</property>
<many-to-one name="kamUser" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3k.basicdata.User"
cascade="none"
fetch="select"
column="KAM_USER_ID"/>
<many-to-one name="kamSubstUser" not-null="false"
lazy="false"
entity-name="ch.deltaenergy.et3k.basicdata.User"
cascade="none"
fetch="select"
column="KAM_SUBST_USER_ID"/>
<property name="debitorNo" type="java.lang.String">
<column name="DEBITOR_NO" length="35" />
</property>
<property name="creditorNo" type="java.lang.String">
<column name="CREDITOR_NO" length="35" />
</property>
<property name="description" type="java.lang.String">
<column name="DESCRIPTION" length="80" />
</property>
<property name="paymentModeId" type="java.lang.Long">
<column name="PAYMENT_MODE_ID" precision="22"
scale="0" />
</property>
<property name="paymentConditionId"
type="java.lang.Long">
<column name="PAYMENT_CONDITION_ID" precision="22"
scale="0" />
</property>
<property name="displayAs" type="java.lang.String">
<column name="DISPLAY_AS" length="80" />
</property>
<bag name="addresses" cascade="all"
where="LINK_TYPE = 'RET_CUSTOMER_KEY'"
lazy="false" optimistic-lock="true" >
<key column="LINK_ID" property-ref="seqPk"
not-null="true"/>
<one-to-many class="ch.deltaenergy.et3000.customermgmt.Address" />
</bag>
</class>
</hibernate-mapping>
note that the collection causing the problem, is the addresses collection, For some weird
reason we had two customer objects with the same property "seqPK".
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate3
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
2:50 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Paul Andrews updated HHH-2862:
------------------------------
Attachment: bug.zip
I've attached a test case which includes tables, data, Java classes, mapping file and
testcase.
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate3
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
2:54 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Paul Andrews updated HHH-2862:
------------------------------
Attachment: testcase.zip
Arghhh. First attachment had empty ddl.sql file. This one should be OK.
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate3
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
9:42 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Alexander Taggart commented on HHH-2862:
----------------------------------------
I too have just run into a similar case whereby a many-to-many join annotation erroneously
used non-unique column instead of the primary key. The following hibernate code (from
org.hibernate.engine.StatefulPersistenceContext) even comments on the issue:
private void addCollection(PersistentCollection coll, CollectionEntry entry, Serializable
key) {
collectionEntries.put( coll, entry );
CollectionKey collectionKey = new CollectionKey( entry.getLoadedPersister(), key,
session.getEntityMode() );
PersistentCollection old = ( PersistentCollection ) collectionsByKey.put( collectionKey,
coll );
if ( old != null ) {
if ( old == coll ) {
throw new AssertionFailure("bug adding collection twice");
}
// or should it actually throw an exception?
old.unsetSession( session );
collectionEntries.remove( old );
// watch out for a case where old is still referenced
// somewhere in the object graph! (which is a user error)
}
}
So, when encountering a case where the collection was associated with a previous entity,
the previous entity's collection wrapper has its session invalidated. The in-code
comment is correct when it states the case "is a user error." It would be great
to get an exception reflecting that fact rather than what actually occurs: nothing until
I iterate over the collection and get a LazyInitializationException red herring.
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate3
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
8:23 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Cristian Dragoste commented on HHH-2862:
----------------------------------------
I encountered the same issue on Hibernate 3.1.3.
On the other side, when when doing a lazy fetch on a non-unique collection the error is
:"lazy initialization exception" even if the session is still open.
Regards, Cristian.
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate3
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
9:08 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Sylvain Veyrié commented on HHH-2862:
-------------------------------------
Same for me with Hibernate 3.2.6 with a map collection mapped with JPA annotations and
Apache Derby.
If my query result is a list of entities that references each a different map content :
OK
If two references the same content (= the @JoinColumn value is the same for two entities),
it leads to "session is closed" - even if session is open (lazy) or
"collection is not associated with any session" (eager)
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate Core
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
5:34 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Kevin Long commented on HHH-2862:
---------------------------------
We are having the exact same problem. +1
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate Core
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
6:18 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Ben Vanberg commented on HHH-2862:
----------------------------------
Same problem here.
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate Core
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
1:52 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Tino Nitze commented on HHH-2862:
---------------------------------
Same here...
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate Core
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
9:59 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862?page=c...
]
Eric Chavet commented on HHH-2862:
----------------------------------
I'm not sure if it was the same problem. But I was having a "Collection is not
associated with any session" on an eager collection.
The real problem was that the bean under the collection did not have any default
constructor.
Collection is not associated with any session exception when doing an
eager fetch on a non-unique collection.
-------------------------------------------------------------------------------------------------------------
Key: HHH-2862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862
Project: Hibernate Core
Issue Type: Bug
Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5
Reporter: Paul Andrews
Attachments: bug.zip, testcase.zip
It is basically caused by having an eager collection where the key of the collection is
not unique in the results.
The code works as follows in CollectionType.getCollection():
....
persistenceContext.addUninitializedCollection( persister, collection, key );
// some collections are not lazy:
if ( initializeImmediately( entityMode ) ) {
session.initializeCollection( collection, false );
}
else if ( !persister.isLazy() ) {
persistenceContext.addNonLazyCollection( collection );
}
if ( hasHolder( entityMode ) ) {
session.getPersistenceContext().addCollectionHolder( collection );
}
if persistenceContext.addUninitializedCollection() detects that the collection with the
given key has already been added it clears the session on the old instance of the
collection (sets it to null). However, that collection has already been added to the
persistence context by an earlier call to this method. So later when
StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through
all of the collections in the persistence context (including those which have had their
session set to null by addUninitializedCollection()), calling forceInitialization() which
throws a 'collection is not associated with any session' exception.
--
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
5434
days inactive
6302
days old
hibernate-issues@lists.jboss.org
11 comments
10 participants
participants (10)
-
Alexander Taggart (JIRA) -
Ben Vanberg (JIRA)
-
Cristian Dragoste (JIRA)
-
Eric Chavet (JIRA)
-
Gail Badner (JIRA)
-
Kevin Long (JIRA)
-
Lorenzo Resta (JIRA)
-
Paul Andrews (JIRA)
-
Sylvain Veyrié (JIRA)
-
Tino Nitze (JIRA)