About Question enthuware.oce-ejbd.v6.2.499 :

[prakashyaji]

Just a small advice:
To be consistent with other explanations, please add following scenario as well to the explanation of option 2.

Existing is : "In case of a server crash or if a system exception is thrown from the instance’s method to the container, the remove() method will not be called."

Also mention that, @PreDestroy method is not called if Timeout occurs when stateful session bean is passivated.
I hope this helps
Thanks,
Prakash Yaji

[admin]

Thank you for your suggestion. This has now been added.
-Paul.

[Christian]

The MDB as displayed is actually not valid: it is not annotated with @MessageDriven, nor does it implement the MessageDrivenBean interface.

Sure, the deployment descriptor could denote it as a MessageDrivenBean, but it could also not do so.

[admin]

If the question says it is a MDB, it can be safely assumed that it is a MDB. Still, it has been added to avoid confusion.

thank you for your suggestion,
Paul.

[aazizi.tarik]

In explanation of option 2: " @PreDestroy method is not called if Timeout occurs when stateful session bean is passivated."
How is that possible while we can't have timers on stateful session beans? Please could you clarify that to me?

[admin]

This timeout is not of the timer here, it is the time the bean can remain idle for want of call from client. As per section 4.3.12:

A Bean Developer or Deployer may optionally assign a timeout value to a stateful session bean. This value is the amount of time a stateful session bean is permitted to remain idle (not receive any client invocations) before being removed by the container.

HTH,
Paul.

[aazizi.tarik]

Thanks Paul, another question that come in mind, in that case does the container count also the time while the bean is passivated?

[admin]

Yes, that is exactly why it removes the bean even it it is in passive state.