Can you control when passivation occurs?

EJB Interview Questions and Answers

(Continued from previous question...)

14. Can you control when passivation occurs?

The developer, according to the specification, cannot directly control when passivation occurs. Although for Stateful Session Beans, the container cannot passivate an instance that is inside a transaction. So using transactions can be a a strategy to control passivation. The ejbPassivate() method is called during passivation, so the developer has control over what to do during this exercise and can implement the require optimized logic. Some EJB containers, such as BEA WebLogic, provide the ability to tune the container to minimize passivation calls. Taken from the WebLogic 6.0 DTD -The passivation-strategy can be either default or transaction. With the default setting the container will attempt to keep a working set of beans in the cache. With the transaction setting, the container will passivate the bean after every transaction (or method call for a non-transactional invocation).

(Continued on next question...)

Other Interview Questions

• Can a Session Bean be defined without ejbCreate() method?
• What happens if remove( ) is never invoked on a session bean?
• What is an EJB Context?
• What is an EJB Context?
• What is a Message Driven Bean, what functions does a message driven bean have and how do they work in collaboration with JMS?
• Brief description about local interfaces?
• How can I call one EJB from inside of another EJB?
• How is persistence implemented in enterprise beans?
• Is it possible to share an HttpSession between a JSP and EJB? What happens when I change a value in the HttpSession from inside an EJB?
• Is there any way to read values from an entity bean without locking it for the rest of the transaction (e.g. read-only transactions)?
• More...