JR50951: HUGE MEMORY CONSUMPTION BY SESSION OBJECTS
Fixes are available
Closed as program error.
If your IBM Business Process Manager server has many users connected, the server's heap might grow to huge values. If you perform a heap dump and analyze it, you can see that a large part of the heap is occupied by WebWorkflowManager objects nested in HTTP session objects. If you perform a heap dump and analyze it, you can see that a large part of the heap is occupied by WebWorkflowManager objects nested in http session objects. com/lombardisoftware/component/common/workflow/EJBWorkflowManage rDelegateDefault com/lombardisoftware/component/common/workflow/EJBWorkflowManage rDelegateWebSphere
IBM BPM keeps a cache of stateful session beans (one session bean for each human service that a user works with). This cache is stored inside the user's HTTP session. The cache update policy removes a stateful session bean from the cache if it has not been accessed for more than one hour. If a user works with multiple human services, many stateful session beans will be in the cache for this user. For human services of user tasks in a business process definition (BPD) instance, the stateful session bean is saved in the database with the associated task; therefore, the cache for these human services is not needed.
A fix is/will be available that modifies the cache so that stateful session beans for human services of user tasks in a BPD instance are no longer kept in the cache. Human services that start directly from IBM Process Portal (exposed as startable) don't have an associated task and, therefore, the cache is not modified for these services. In addition, this fix makes the cache timeout configurable. To modify the default timeout (60 minutes), edit 100Custom.xml, which is located in the following directory: <profile-root>/config/cells/<cell-name>/nodes/<node-name>/server s/<server-name>/<server-type>/config where <server-type> can be either process-center or process-server. Add the following definition to the <server> element: <web-workflow-manager merge="mergeChildren"> <session-bean-cache-expiry-timeout>timeout in minutes </session-bean-cache-expiry-timeout> </web-workflow-manager> An example 100Custom.xml that sets the timeout value to 50 minutes would look like this: <properties> <server> <web-workflow-manager merge="mergeChildren"> <session-bean-cache-expiry-timeout>50 </session-bean-cache-expiry-timeout> </web-workflow-manager> </server> </properties> If your processes run on a cluster, you must make this change for each cluster member. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR50951: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select APAR or SPR, enter JR50951, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels