[ http://jira.jboss.com/jira/browse/JBAS-5474?page=comments#action_12410924 ] Emmanuel Bernard commented on JBAS-5474: ---------------------------------------- Can you attach a runnable test case (the domain model would be sufficient) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5474?page=com.atlassian.jira.plug... ] Emmanuel Bernard commented on JBAS-5474: ---------------------------------------- Something like that http://anonsvn.jboss.org/repos/hibernate/entitymanager/trunk/src/test/org... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5474?page=com.atlassian.jira.plug... ] Emmanuel Bernard commented on JBAS-5474: ---------------------------------------- Sorry I failed to put myself in some outsider's shoes Check out this page http://www.hibernate.org/6.html#A4 to checkout entitymanager (the project) Then check out http://hibernate.org/449.html (basically run ant clean junit) => this should work from there, you will find both the test cases I was pointing to and the superclass in src/test HTH -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5474?page=com.atlassian.jira.plug... ] Andrew DePue commented on JBAS-5474: ------------------------------------ We are running into this same issue. We access the size() of the association in the setter method, and run into the LazyInitializationException even though it is a FetchType.EAGER association. We are using Hibernate directly (not in JBossAS) v. 3.2.6.ga. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5474?page=com.atlassian.jira.plug... ] arjan tijms commented on JBAS-5474: ----------------------------------- Same issue and apparently still no resolution. When accessing the association in the setter method, the following exception is thrown: 12:14:11,327 ERROR [LazyInitializationException] failed to lazily initialize a collection, no session or session was closed org.hibernate.LazyInitializationException: failed to lazily initialize a collection, no session or session was closed at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:380) at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:372) at org.hibernate.collection.AbstractPersistentCollection.readSize(AbstractPersistentCollection.java:119) at org.hibernate.collection.PersistentSet.size(PersistentSet.java:162) at java.util.LinkedHashSet.<init>(LinkedHashSet.java:151) While accessing the association in the @PostLoad annotated method throws a different exception: org.hibernate.LazyInitializationException: illegal access to loading collection at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:363) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:108) at org.hibernate.collection.PersistentSet.iterator(PersistentSet.java:186) In the last case, Hibernate explicitly checks whether the collection is still 'initializing', thus it's not related to any persistence context being closed. I'm not sure why the first exception does say that. Is that a bug in the exception that is thrown due to this bug? The code that throws the exception when accessing the association in the @PostLoad method is the following: /** * Initialize the collection, if possible, wrapping any exceptions * in a runtime exception * @param writing currently obsolete * @throws LazyInitializationException if we cannot initialize */ protected final void initialize(boolean writing) { if (!initialized) { if (initializing) { throw new LazyInitializationException("illegal access to loading collection"); } throwLazyInitializationExceptionIfNotConnected(); session.initializeCollection(this, writing); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-5474?page=com.atlassian.jira.plugin.sy... ] henk de boer commented on JBAS-5474: ------------------------------------ Why is an issue such as this still open after more than 2 years? I have the exact same problem. I have an eagerly loaded association for a collection of entities. For performance reasons I would like to create an internal Set for some property of these entities. Either the setter or the @PostLoad would be a clean and simple place to create this, yet Hibernate won't let me because of this silly exception. I now have to code a very ugly workaround, where I manually track stuff and build this Set after the first to its setter. This works, but it's verbose, ugly and brittle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-5474?page=com.atlassian.jira.plugin.... ] Setanta Mathews commented on JBAS-5474: --------------------------------------- This was a hibernate jpa entity manager related issue. Using a version of the attached code I can confirm that it still exists in 3.6.2.Final hibernate release. This was the second most popular issue before it was closed. For an existing problem, it's a real shame that these votes are essentially thrown away. I will open an issue in the relevant hibernate project and link back to this one. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira