Fixes are available
APAR status
Closed as program error.
Error description
Lazy memory pool initialization is not guarded and it mau cause a crash, if there is a racing between two active classes (threads), which both send the same event (event of the same type).
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Memory pool initialization is not guarded.
Problem conclusion
In version 8.0.1, changes were made to the framework in order to solve this problem. Now you can define OM_USE_STATIC_MEMORY_POOL_INITIALIZATION macro in omosconfig.h and recompile the framework. This will result in initialization of static memory pool in the pre-main phase of runtime execution. Note that this flag cannot be used if the user defines their own memory manager.
Temporary fix
Comments
APAR Information
APAR number
PM58878
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
752
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-23
Closed date
2012-11-27
Last modified date
2012-11-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TLOGIC RHAPSODY
Fixed component ID
5724V74RP
Applicable component levels
R752 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.2","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
06 January 2022