Noteworthy Resolved Issues

3 Noteworthy Resolved Issues

This following table highlights specific key fixes that are included in this release. In some cases, only a percentage of the overall fixed defects are listed.

Affected Component	Defect Number	Summary
Execution Engine	N/A	The Execution Engine is the component of POM responsible for sending job execution requests for those jobs that are ready to run. The engine idles when it has no requests for execution and wakes up when requests became available. . In previous versions on POM, there were instances when a request would fail to wake the engine up. This is corrected in POM 19.1.010. Additionally, a safeguard is added to wake the engine up occasionally to check for requests.
Batch Scheduler	33275642	BATCH SCHEDULER TASK FAILURE. Adhoc scheduler tasks that were systematically cancelled by POM when nightly started, were being marked as ERROR. Failure notifications were being sent when these were not really failures.
Batch Scheduler	32820419	POM CYCLE JOBS WITH CRITICAL ERROR NOTIFICATION ON THE MONITORING SCREEN. Error notifications were being sent intermittently when multiple nodes in a clustered environment conflicted over handling the same scheduler task.

Affected Component

Defect Number

Summary

Execution Engine

N/A

The Execution Engine is the component of POM responsible for sending job execution requests for those jobs that are ready to run. The engine idles when it has no requests for execution and wakes up when requests became available. . In previous versions on POM, there were instances when a request would fail to wake the engine up. This is corrected in POM 19.1.010. Additionally, a safeguard is added to wake the engine up occasionally to check for requests.

Batch Scheduler

33275642

BATCH SCHEDULER TASK FAILURE.

Adhoc scheduler tasks that were systematically cancelled by POM when nightly started, were being marked as ERROR. Failure notifications were being sent when these were not really failures.

Batch Scheduler

32820419

POM CYCLE JOBS WITH CRITICAL ERROR NOTIFICATION ON THE MONITORING SCREEN.

Error notifications were being sent intermittently when multiple nodes in a clustered environment conflicted over handling the same scheduler task.