ENGINE Failure on multiple blades. Application server down while engine fails to pass blades (Doc ID 1395175.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Demantra Demand Management - Version: 7.3.0.1 and later   [Release: 7.3.0 and later ]
Information in this document applies to any platform.
How to run ENGINE on multiple blades instances

Symptoms

The mentioned patch was applied on dev which was on different blade, but the engine failed to switch to next blade for QA which had 2other blades on the same machine

Changes

Applied the patch <Bug:12654186> as part of installing:

7.3.0.2 - <Patch:12823079> includes the following fixes:

<BugDB:12823079> - DEMANTRA ENGINE ERROR FAILED TO RETRIEVE HISTORY INFORMATION
<BugDB:12716649> - TOMCAT DIES WHEN THE SIMULATION ENGINE IS STOPPED.
<BugDB:12654186> - TOMCAT DOWN DURING FORECAST ENGINE RUN. ENGINE NOT RUN COMPLETE.
<BugDB:12836903> - ENGINE ERROR
<BugDB:12871738> - WEB SERVER IS GETTING DOWN AUTOMATICALLY AFTER DEPLOYING ENGINE ON LINUX IN DIST

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms