A fix is available
Closed as program error.
In Process Designer, while saving a Coach after adding a button (or something else) everything's ok in the first 3 Saves There is a slight delay in response time between each save but it works. Then, when we make the 4th save, Process Designer stops responding There is a "Saving" message and in the window title a "Not Responding" for a while. After that a new window "Refreshing Library" also with "Not Responding". After this, Process Designer stops working and in the installation folder some heapdumps and javacore dumps are created. The Process Designer interface, becomes grey and not working We are able to kill the process and restart. The described sequence happens again - 3 saves OK, 4 save KO.
If user is working in a fairly large process application or toolkit, with many coach views, Process Designer will run out of memory after a short amount of time after doing a variety of actions (such as saving changes to editors, or even opening/closing coach view artifacts). USER AFFECTED: Business Process Manager Advanced, Standard and Express users leveraging New Generation Coaches and Coach views in a fairly large workspace. PROBLEM DETAILED DESCRIPTION: Code change introduced in 8.0.1 included a static resource. The static resource set, while improving temporal performance, introduced a memory leak because all loaded layouts were never being released from memory.
Removed the static resource set, and introduced proper resource set usage while still maintaining temporal performance goals. FIX AVAILABILITY: Fix for 8.0.1 is available on Fix Central, search for APAR JR45226 at http://www.ibm.com/support/fixcentral/ Fix for 126.96.36.199 is available on Fix Central, search for APAR JR45226 at http://www.ibm.com/support/fixcentral/ When downloading fix package from Fix Central, please ensure to download and thoroughly review the complimentary readme, which includes install instructions, and more info about the particular fix.
Reported component name
Reported component ID
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