IO can crash with error message in dump involving MU variables management
search cancel

IO can crash with error message in dump involving MU variables management

book

Article ID: 86317

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Error Message :
 In IO dump after crash, we can see the number of variables is not the right number ( 20 variables expected, over 85 millions loaded ) : 
##########################
2013-05-30 18:38:14 |INFO |X|IO |pid=26932.32580| u_load_target_elt | Target B000000072 loaded, 20 variable(s) 
2013-05-30 18:38:14 |TRACE|X|IO |pid=26932.32580| u_trt_req_objget | 85127192 variable(s) loaded for Target B000000072 
2013-05-30 18:38:14 |INFO |X|IO |pid=26932.32580| IOUnhandledExceptionFilte | *** execution handler: TID=(32580)

In universe.log ( this error message is not specific to this error, please check the IO dump ) : 
| 2013-05-30 18:38:14 |INFO |X|IO |pid=26932.32580| IOUnhandledExceptionFilte | *** execution handler: TID=(32580)
##########################  

Patch level detected:Dollar Universe 6.0.00
Product Version: Dollar.Universe 6.0.0

Description :Under heavy load, when launching jobs to a Management Unit with MU variables using HDP, IOserv can crash with error message in dump involving MU variables management.
Having Reporter extracting data in the same time of a big HDP launch to a lot of MU with variables have been proven to catalyse this situation.
This (rare) behaviour has only been reproduced on Microsoft Windows (2003, 2008), however, it's not impossible that other OS could be impacted.

Environment

OS: Windows
OS Version: All

Cause

Cause type:
Defect
Root Cause: The way memory was managed when loading Management Unit variables values seems to have a defect which appears only under certain heavy load circumstances in Dollar Universe up to version 6.0.14.

Resolution

This is fixed in Dollar Universe 6.0.15 and above.

Fix Status: Released

Fix Version(s):
Component: Application.Server
Version: Dollar.Universe 6.0.0
Dollar Universe 6.0.15

Additional Information

Workaround :
N/A