Removing session bean twice - strange effects in JBoss

Discussion in 'Java' started by Alex Molochnikov, Oct 6, 2005.

  1. My code erroneously sent remove() call to a stateful session bean's remote
    interface twice. The first call triggered ejbRemove() method on the bean,
    but the second call (to an already removed bean) sent it into a new creation
    cycle, calling setSessionContext() method (and the stack trace shows create
    methods from the container).

    Should it not have thrown an exception instead? Did anyone experience
    something like this? I am running JBoss 4.0.1 SP1 on Win XP Pro under Java
    1.5.0-04.

    Alex Molochnikov
    Gestalt Corporation
     
    Alex Molochnikov, Oct 6, 2005
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. David Thielen
    Replies:
    2
    Views:
    834
    Marek Lange
    Sep 12, 2003
  2. tmaus
    Replies:
    1
    Views:
    508
    Sudsy
    Sep 17, 2004
  3. X3
    Replies:
    0
    Views:
    432
  4. Replies:
    1
    Views:
    417
    Manish Pandit
    Sep 13, 2006
  5. Francesco
    Replies:
    3
    Views:
    500
Loading...

Share This Page