Даже если в приложении в web.xml стоит например
<session-config>
<session-timeout>60</session-timeout>
</session-config>

Приложение может уже через полчаса удалить Ваш SessionBean и Вы получите NoSuchEjBException

Чтобы этого избежать, надо в Jboss5_Home/server/default/deployers/jbossweb.deployer/web.xml
поменять настроики для session timeout для всех приложений

JBoss 5 allows you to define a session timeout for all applications at:

deployers/jbossweb.deployer/web.xmlIt may be that is overriding your settings in web.xml. It shouldn't, but, you know...

Check if changing that is working. If not, you can set up the timeout programatically for your test:

HttpSession.setMaxInactiveInterval(int seconds)

That way you can force the timeout in a particular session.

Blazkowicz,

28.8. Configuring SFSB and Session Timeouts in JBoss AS

The timeout for stateful session beans must be longer than the timeout for HTTP sessions, or the stateful session bean may timeout before the user's HTTP Session ends. The JBoss AS has a default session bean timeout of 30 minutes, which is configured in server/default/conf/standardjboss.xml — to change this, replace default with your own preferred configuration.

In the LRUStatefulContextCachePolicy cache configuration, modify the value of max-bean-life to change the default stateful session bean timeout:
<container-cache-conf>
<cache-policy>
org.jboss.ejb.plugins.LRUStatefulContextCachePolicy
</cache-policy>
<cache-policy-conf>
<min-capacity>50</min-capacity>
<max-capacity>1000000</max-capacity>
<remover-period>1800</remover-period>

<!-- SFSB timeout in seconds; 1800 seconds == 30 minutes -->
<max-bean-life>1800</max-bean-life>

<overager-period>300</overager-period>
<max-bean-age>600</max-bean-age>
<resizer-period>400</resizer-period>
<max-cache-miss-period>60</max-cache-miss-period>
<min-cache-miss-period>1</min-cache-miss-period>
<cache-load-factor>0.75</cache-load-factor>
</cache-policy-conf>
</container-cache-conf>

You can modify the default HTTP Session timeout in server/default/deployer/jboss-web.deployer/conf/web.xml for JBoss Enterprise Application Platform 5.1. The following entry in the web.xml file controls the default session timeout for all web applications:
<session-config>
<!-- HTTP Session timeout, in minutes -->
<session-timeout>30</session-timeout>
</session-config>

To override this value for your own application, simply include a modified version of this entry in your application's own web.xml.

Вот еще один способ решения



I am using EJB3 with Jboss 5.1.0.GA and have successfully set this value in JBOSS_HOME/deploy/transaction-jboss-beans.xml.

The default was 300 in <property name="transactionTimeout">300</property>



http://stackoverflow.com/questions/2184844/jboss-transaction-timeout-setting