Question & Answer
Question
The default value of Session Bean Timeout in BPM is 7200 seconds. If you get SessionBeanTimeoutException, you have to increase Session Bean Timeout value. How do you change the default value?
Answer
The change requires you to modify the Teamworks.ear file and redeploy the application to your IBM Business Process Manager server or cluster. Complete the following steps:
- Make a copy of the <BPM_root>/BPM/Lombardi/process-server/applications/Teamworks.ear file and name it Teamworks.zip.
- Decompress the Teamworks.zip file into a temporary directory.
- Open the twcore-ejb.jar file, which exists in the Teamworks.zip file and extract the /META-INF/ibm-ejb-jar-ext.xmi file to the C:/META-INF/ directory.
- Open the ibm-ejb-jar-ext.xmi file in a text editor.
- Change the following line to update the timeout setting as the value you want.
<ejbExtensions xmi:type="ejbext:SessionExtension" mi:id="SessionExtension_1088097409140" timeout="7200">
Note: There are two statements in this XMI file. These statements are for different beans: one for Session_5 and one for Session_6. You only need to edit the statement called out previously, which is Session_5 for the EjbWorkflowManager.
- Save your changes to the ibm-ejb-ext.xmi file.
- Update the twcore-ejb.jar file with the modified ibm-ejb-jar-ext.xmi file. Be sure that the path information for the file remains as /META-INF/.
- Open the /META-INF/MANIFEST.MF file in a text editor.
- Make a change for Implementation-Version and then save it.
- Open the <BPM_root>/BPM/Lombardi/process-server/applications/Teamworks.ear file.
- Update the teamworks.ear archive with the updated twcore-ejb.jar file and MANIFEST.MF file. Again, be sure that the path information for this file remains correct. No additional path information should be stored for this file.
- Run the BPMProfileUpgrade command on IBM Business Process Manager Version 7.5.1.x and 8.0.1.x or the BPMConfig command on IBM Business Process Manager Version 8.5.0.x to update the EAR file to the existing server or cluster.
- On IBM Business Process Manager Version 7.5.1 and later fix packs and also 8.0.1 and later fix packs, see the following information:
- For stand-alone servers, see step 3 in the Updating a stand-alone profile for an interim fix document.
- For clusters, see step 7 in the Updating profiles in a network deployment environment for an interim fix document.
- On IBM Business Process Manager Version 8.5.0 and later fix packs, see the following information:
- For stand-alone servers, see step 3 in the Updating a stand-alone profile for an interim fix document.
- For clusters, see step 3 in the Updating profiles in a network deployment environment for an interim fix document.
[{"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Security","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0.1;8.0;7.5.1;7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Security","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0.1;8.0;7.5.1;7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSFTBX","label":"IBM Business Process Manager Express"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Security","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0.1;8.0;7.5.1;7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Historical Number
80835;6X3;760
Product Synonym
BPM
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21601357