1 Reply Latest reply on Jul 3, 2012 6:35 AM by olli24

JBoss7 Remove Timeout for Stateful Session EJB2

olli24 Jul 2, 2012 8:00 AM

Hello.

Could anyone help me with following issue?

I am moving our application from JBoss5 to JBoss AS 7.1.1.Final "Brontes".

We are using Stateful Session Beans (EJB2).

It seems that for SFSB of version EJB2 the remove timeout is infinite. I mean the timeout, after the server removes the EJB instance of a crashed client.

I faced this by killing my EJB client without proper calling the remove() method of the remote interface. On server side ejbRemove() is never called, but should be after the remove timeout has expired.

JBoss5 had in the standardjboss.xml following setting:

<max-bean-life>90</max-bean-life>

How can I set via JBoss7 configuration (or EJB deployment descriptor) the EJB2 remove timeout for Stateful Session Beans?

Moving to EJB3 and using the StatefulTimeout annotation is not a solution, because I need to be compatible to another server which has no EJB3 support.

Are there any limitations in the EJB2 support of JBoss 7.1.1?

Thanks in advance for any information.

Olli

1. Re: JBoss7 Remove Timeout for Stateful Session EJB2

olli24 Jul 3, 2012 6:35 AM (in response to olli24)

Following changes in the ejb-jar.xml are needed to solve the problem.

1) Change schema to ejb-jar_3_1.xsd
2) Set element <stateful-timeout> for each SFSB

For example:

<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns = "http://java.sun.com/xml/ns/javaee"
         version = "3.1"
         xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation = "http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd">
    <enterprise-beans>
        <session>
..
            <stateful-timeout>
                <timeout>1</timeout>   
            </stateful-timeout>
…
      </session>

Now after the stateful timeout has expired, ejbRemove() is called by the server.
Actions