|
From: Rory P. (JIRA) <nh...@gm...> - 2011-04-23 01:20:26
|
Patch to prevent "org.hibernate.AssertionFailure: possible non-threadsafe access to the session" error caused by stateless sessions
-----------------------------------------------------------------------------------------------------------------------------------
Key: NH-2669
URL: http://216.121.112.228/browse/NH-2669
Project: NHibernate
Issue Type: Patch
Components: Core
Affects Versions: 3.2.0Alpha2, 3.2.0Alpha1, 3.1.0, 3.0.0.GA, 3.0.0.CR1, 3.0.0.Beta2, 3.0.0.Beta1, 3.0.0.Alpha3, 3.0.0.Alpha2, 3.0.0.Alpha1, 2.1.2.GA, 2.1.1.GA, 2.0.1.GA, 1.2.1, 3.2.0Alpha3
Reporter: Rory Plaire
Priority: Minor
Attachments: NH-2669.patch
This is a patch copied from Hibernate 3.6.3 and tracked here: https://issues.jboss.org/browse/JBPAPP-3737
==========
In a stateless session, queries load objects in a two-phase process: in the first phase, a temporary persistence context is populated with empty objects; in the second phase, the objects' member data is read from the database. If an object contains an association or a collection, the query performs a recursive call to the session's get() method. This clears the temporary persistence context.
If the parent object contained any other associations to be read as part of the second phase, Hibernate threw an assertion because the associations cannot be found in the persistence context.
This has been fixed by introducing a new method: <literal>org.hibernate.engine.PersistenceContext.isLoadFinished()</literal>. This method tells StatelessSession when to clean the temporary persistence context.
==========
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|