up to now, I thought it would be easy: A stateful EJB SessionBean gets passivated by the container, and as soon as another bean tries to access this bean, it activates itselves.
Not in my code. The Sessionbean works beautifully. When it passivates, it does that without errors or exceptions. When I try to talk to it with the same methods, i used before, my calls get stuck, without warning, errors and so.