Discussions

EJB design: Bean destruction on System Exception

Bookmark and Share Get thread feed

  1. Bean destruction on System Exception (5 messages)

    Please can someone just confirm, does a bean get destroyed if it throws a System exception?

    Cheers.
    Reply to this

    Threaded Messages (5)

  2. Bean destruction on System Exception[ Go to top ]

    In EJB 2.0 (and 1.1 I think), a stateful session EJB instance is destroyed if a Runtime exception is thrown.

    Reply to this Reply to original

  3. Bean destruction on System Exception[ Go to top ]

    In EJB 2.0 (and 1.1 I think), a stateful session EJB instance is destroyed if a Runtime exception is thrown.

    Reply to this Reply to original

  4. Bean destruction on System Exception[ Go to top ]

    The statefull session bean instance is destroyed if:
    - system exception occurs during bean method execution
    - timeout occurs
    (this works for EJB 1.1 and later)

    Wojtek
    Reply to this Reply to original

  5. Bean destruction on System Exception[ Go to top ]

    Does this also apply the same for stateless and entity beans?
    Reply to this Reply to original

  6. Bean destruction on System Exception[ Go to top ]

    1. Entity Beans
    Entity bean is destroyed (in terms of Object.finalize) by the container. Only passivated entity beans can be destroyed. The container is also responsible for passivation.
    From logical point of view (only logical) the Entity Bean instance is destroyed after client calls remove (data is removed from the database).
    2. Stateless Session Bean
    All operations are container initiated. You can set maxBeans and initial bean number in deployment descriptor. You should not make an assumption that you will connect again to the same stateless session bean.

    Regards

    Wojtek
    Reply to this Reply to original