What happens if remove( ) is never invoked on a session bean?

EJB Interview Questions and Answers

(Continued from previous question...)

19. What happens if remove( ) is never invoked on a session bean?

In case of a stateless session bean it may not matter if we call or not as in both cases nothing is done. The number of beans in cache is managed by the container. In case of stateful session bean, the bean may be kept in cache till either the session times out, in which case the bean is removed or when there is a requirement for memory in which case the data is cached and the bean is sent to free pool.

(Continued on next question...)

Other Interview Questions

• Does RMI-IIOP support code downloading for Java objects sent by value across an IIOP connection in the same way as RMI does across a JRMP connection?
• What is the difference between EJB and Java beans?
• What is the difference between Message Driven Beans and Stateless Session beans?
• The EJB container implements the EJBHome and EJBObject classes. For every request from a unique client, does the container create a separate instance of the generated EJBHome and EJBObject classes?
• What is a Message Driven Bean, what functions does a message driven bean have and how do they work in collaboration with JMS?
• Is is possible for an EJB client to marshal an object of class java.lang.Class to an EJB?
• What is session Facade?
• Why is ejbFindByPrimaryKey mandatory?
• The EJB container implements the EJBHome and EJBObject classes. For every request from a unique client, does the container create a separate instance of the generated EJBHome and EJBObject classes?
• For Entity Beans, What happens to an instance field not mapped to any persistent storage, when the bean is passivated?
• More...