org.hibernate.LazyInitializationException

[veeseekay]

guys, am facing an issue while trying to lazy load certain entities withing a multithreaded enviornment.

here s my scenario :

Class Outer {

//Am using jboss rules session
private rulesSession;

private class Inner implements Runnable {

run() {

}

private lazyLoadEntites() {
// this is where I get the damn exception

}

private assertToSession() {
rulesSession.assert(something);
}
}


method() {
// this creates multiple threads to do some job in parallel
// am using executors, and am executing run() of inner class
}
}


and here s my exception

13:50:48,462 ERROR [LazyInitializationException] failed to lazily initialize a collection of role:no session or session was closed
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: no session or session was closed
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358)
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:3

at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:343)


F1 please!!

[waynebaylor]

if you're running within an application server, you shouldn't be creating your own threads. the AS performs thread management for you.

your exception is probably because you've started a new thread but haven't properly associated a session with it.

[veeseekay]

hmmm...i am surprised to knw that I am not supposed to create my own threads within the AS...
My situation is that I have to perform some job over the ntw and it cannot be done serially, i need multi threading to speed up the job.

[waynebaylor]

here's an older link that contains some good info:
http://www.theserverside.com/discussions/thread.tss?thread_id=11031

i think the suggestion of using Message Driven Beans is a good one.