This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
newbie to mdb... i'm developing an mdb with jbuilder8 ee the onMessage method probably does'nt catch an exception i've setted the maximum pool size for the bean container to ten when i run the application the bean is created, then runs into exception, it goes into kill state, but the memory in use is not freed up i'm deploying my mdb bean on a bes 5.2 can someone help me freeing up the memory?? do i need to explicitly call the ejbRemove method? please answer me if you need more explanations... thanks in advance daniela
Originally posted by daniela genitiempo: do i need to explicitly call the ejbRemove method?
No. The Container will handle calling the ejbRemove method. Unfortunately, you don't really supply enough information about what you are doing to be very helpful. Is the exception thrown a System or Application Exception (the ejb container will only remove instances that have thrown a system exception)? How do you know the memory is not being freed? What exactly is the MDB doing?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com