19.4.2. Set Default Session Bean Access Timeout Values
Procedure 19.15. Set Default Session Bean Access Timeout Values using the Management Console
- Login to the Management Console. See Section 3.4.2, “Log in to the Management Console”.
- Click on in the top right, expand the item in the Profile panel on the left and select . Then select the tab from the main panel.

Figure 19.9. EJB3 Container Configuration panel in the Management Console (Standalone Server)
- Click the button. The fields in the Details area are now editable.
- Enter the required values in the Stateful Access Timeout and/or Singleton Access Timeout text boxes.
- Click the button to keep the changes, or click the Cancel link to discard them.
- The Details area will now be non-editable and display the correct timeout values.
Procedure 19.16. Set Session Bean Access Timeout Values Using the CLI
- Launch the CLI tool and connect to your server. Refer to Section 3.5.4, “Connect to a Managed Server Instance Using the Management CLI”.
- Use the
write-attributeoperation with the following syntax./subsystem=ejb3:write-attribute(name="BEANTYPE", value=TIME)
- Replace BEANTYPE with
default-stateful-bean-access-timeoutfor Stateful Session Beans, ordefault-singleton-bean-access-timeoutfor Singleton Session Beans. - Replace TIME with the required timeout value.
- Use the
read-resourceoperation to confirm the changes./subsystem=ejb3:read-resource
Example 19.12. Setting the Default Stateful Bean Access Timeout value to 9000 with the CLI
[standalone@localhost:9999 /] /subsystem=ejb3:write-attribute(name="default-stateful-bean-access-timeout", value=9000)
{"outcome" => "success"}
[standalone@localhost:9999 /]Example 19.13. XML Configuration Sample
<subsystem xmlns="urn:jboss:domain:ejb3:1.2">
<session-bean>
<stateless>
<bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
</stateless>
<stateful default-access-timeout="5000" cache-ref="simple"/>
<singleton default-access-timeout="5000"/>
</session-bean>
</subsystem>

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.