If a 32-bit JRE is missing, the engine will enter a continuous restart loop.

Symptoms:

• The engine service fails to stay in a "Running" state and restarts repeatedly.

• Engine Logs: Logs will indicate a failure during the "Loading Grid Library" phase.

• Error Message: The logs typically provide a generic loading error rather than a specific alert regarding the missing 32-bit architecture.
  
  Note: The error message does not explicitly state that a "32-bit JRE is missing," making it difficult to diagnose without checking configuration settings.

Cause:

This behavior occurs when the engine configuration is set to a 32-bit platform, but the Grid Library repository only contains 64-bit JREs or lacks a JRE compatible with the 32-bit Grid Library service.

This issue is specific to legacy versions of the software.

To resolve the restart loop, ensure that a compatible 32-bit JRE is uploaded and configured:

1. Verify Configuration: Confirm that the engine configuration is indeed set to the 32-bit platform. Check the Additional platform property on the Engine configuration page from UI.

2. Check Grid Libraries: Navigate to the Grid Library section from the UI console.

3. Upload JRE: If no 32-bit JRE is present, upload a supported 32-bit JRE version.

4. Restart Service: Once the 32-bit JRE is available in the library, the engine should successfully load the libraries and stabilize.

In environments configured to run 32-bit services with 32-bit Platform Engines, the service requires at least one 32-bit Java Runtime Environment (JRE) to be present within the Grid Library section.