Even im facing the same problem i am not getting help any where in the web...iw onder if there is something to it.
Why are we not getting any responses for this post can some body please help us in understanding the situation that is being faced by us?
We are using stateless session bean and we are facing the same problem as mentioned in this post. Though we are invoking remove im not sure if these instances are moved back to the pool.
Thanks for the response. I have couple of questions please let me know the answers.
1. I checked JIRA and do this mean updating to JBossAS-5.0 Alpha or JBossAS-4.0.4RC1 will fix the problem?
2. My customer might not agree to this, is there a way where i can just patch this bug alone?
3. If i upgrade to newer version then i might face new problems where can i get the list of them?
Did you find a solution for this behavior? Our application dies after working for 4 weeks, and we've narrowed it down to the ejbCreates being called, but no ejbRemoves being done.
i need your help , how did you fix the problem
Also please tell me how can we check the instances of the beans with JBoss' web-console
Waiting for your reply
I am using JBoss 3.2.6 as server and I am deploying stateless session beans over it, but as according to the documentation JBoss is not making the pool for them and making more instances of the beans more than the pool size defined there in standardJboss.xml ... The EJBRemove that is called by server is not being called by the server
I am checking the instances of the beans with JBoss' web-console. The number of instances increases on new requests.
If someone can, then help help me I am in a great trouble ...