Error 500 and LazyInitializationException when adding trim points to jobstreams

Products

• Automation Analytics & Intelligence

Issue/Introduction

When executing the trim point script or attempting to manually add or remove trim points via the Web UI, the operation fails and returns a 500 Internal Server Error․ The backend logs record a LazyInitializationException indicating that memory is out of sync with the database․​​​​‌​‍

ERROR MESSAGE: "Exception something went wrong: (500) Reason: Internal Server Error" "org․hibernate․LazyInitializationException: failed to lazily initialize a collection of role: com․termalabs․common․hibernate․jaws․JobStream․jobs: could not initialize proxy - no Session" "java․lang․NullPointerException"

SYMPTOMS:

• Command line scripts fail immediately with a 500 error

• Web UI fails to save manual trim point changes

• User interface becomes unresponsive and jobstream definition pages do not load

• Log files repeat Could not associate runs jammer errors

CONTEXT: Occurs during the initialization phase for updating jobstream objects, specifically when adding or editing large jobstreams․ IMPACT: Prevents configuring large jobstreams to a manageable number of jobs, leading to performance issues․

Environment

AAI 24.3

Cause

A product defect (DE181112 / DE180483) causes an exception when accessing jobstream objects during the initialization phase for an update․ This exception indicates that memory is out of sync with the content of the database․

Resolution

1․ UPGRADE TO VERSION 24․4․0

Path: Broadcom Download Portal

EXPECTED: The initialization exception is resolved and trim points save successfully NOTE: The fix is included in release 24․4․0

2․ UPDATE EEM POLICIES

Action: If using EEM, migrate your policies and users after the upgrade

EXPECTED: Authentication functions correctly post-upgrade NOTE: Review the EEM Update/Migration Instructions for specific steps

3․ INCREASE DATABASE TABLESPACE

Action: Consult with your database administrator to increase the INDICES tablespace for the application database

EXPECTED: The schema upgrade completes successfully NOTE: The schema update includes a new index (XIE14JobRun) on the JobRun table, requiring extra space and additional time during creation

VERIFY SUCCESS:

• Trim points can be added via script without 500 errors

• Trim points can be saved manually in the Web UI

• Log files no longer show initialization errors