Stateless Bean with @PreDestroy-Annotation on WildFly 8 Final

[peterlustig]

Hello everyone,

I have a Webapplication (WAR-Archive) within a EAR-Application an in this WebApp I have a Stateless Session Bean (SLSB) that connects to a database for example.

This SLSB has a method annotated with @PreDestroy to close the connection cleanly when the EJB-Container wants to destroy the instance of the SLSB.

I can give a simple example:

@Stateless

public class DatabaseConnectorBean {

   public void start() {

     //open connection to database and do some stuff...

   }

    @PreDestroy

    public void stop() {

    // close the connection before destruction

    }

}

The SLSB is injected and used in a RESTful-Webservice where I can call the start() and stop() methods. When I call the start() method and it returns then the stop() method (annotaded with @PreDestroy) is called immediately.

When I remove the @PreDestroy-Annotation the stop() method wasn't called understandably.

I don't know why the EJB-Container wants to destry the instance direct after creation?

When I annotate the EJB with @Singleton the instance will not be destroyed after creation.

Maybe someone can explain what is happening?!

Many thanks in advance and regards,

Peter

[sfcoy]

What is the lifecycle of your "RESTful-Webservice" implementation?

As you are using a stateless session bean, it's lifecycle is closely coupled with the object into which it is injected.

[peterlustig]

Hello Stephen,

thank you for your answer. I know that the lifecycles are closely coupled together. But I don't think that the SLSB is destroyed because of the destruction of the RESTful-Webservice. The webservice is still there.

In addition: I noticed this behaviour only with Wildfly 8 Final, neither with JBoss AS 7.1.1 Final or Glassfish 4.

Thanks in advance and regards,

Peter

[welle]

In WildFly 8.0.0.Final SLSB instance pooling is disabled by default This means that each call creates it's own instance that just lives for the duration of the call.

Try to enable pooling by the following CLI command:

    /subsystem=ejb3:write-attribute(name=default-slsb-instance-pool,value=slsb-strict-max-pool)

[peterlustig]

Hello Anders,

thank you for your answer - I think that was the right hint. Now it works as I knew it from the other application server.

Now I wonder if I've used SLSB in the wrong way in the past...

Thank you very much for the helpful answer!

Regards

Peter

PS: Thanks to Stephen, too.