[jboss-user] [EJB/JBoss] - Warning

2009-06-18 Thread alex0027
Hi, I'm using a ejb2 stateful session beans on JBoss 4.0.5.GA. If this stateful bean should be passivated I get the warning (for several different bean instances): 07:42:03,556 WARN [AbstractInstanceCache] Unable to passivate due to ctx lock, id=fw31kjyx-1i This warning repeats every 5 minut

[jboss-user] [EJB 3.0] - Re: stateful session bean is not removed from memory

2009-04-07 Thread alex0027
I think this is a bug in the ejb3 implementation of jboss stateful session beans. I've changed my bean to a ejb2 bean and the bean is evicted correct from memory. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224005#4224005 Reply to the post : http://www.jb

[jboss-user] [EJB 3.0] - Re: stateful session bean is not removed from memory

2009-04-02 Thread alex0027
I've analyzed the Heapdump and there is a reference from "org.jboss.ejb3.stateful.StatefulBeanContext" to my stateful bean. Shouldn't be this reference deleted after "destroy" the bean? Perhaps this is the problem why the garbage collector not remove my bean. View the original post : http://www

[jboss-user] [EJB 3.0] - stateful session bean is not removed from memory

2009-04-02 Thread alex0027
Hi, we are using EJB 3 stateful session beans on JBoss 4.2.2.GA (jems-installer-1.2.1.CR4.jar). Our application creates a lot of instances of one stateful bean. About 300 per minute. So we set the timeouts to: ... idleTimeoutSeconds=30, removalTimeoutSeconds=30 ... At the proper time the "@PreD