Try OpenEdge Now
skip to main content
BPM Events User's Guide
Administering and operating BPM Events : Troubleshooting cases : Fixing with full recovery

Fixing with full recovery

Troubleshooting Scenario #1: To fix with full recovery.
1. Bring the stalled server to a STOPPED state, with the BPM Events Admin utility ("Stop" command). After this operation, the engine state is not lost, but ready for recovery from the database (except for the current event which requires reprocessing).
2. Fix the problem (for example, database server, or process engine availability).
3. Restart the server with the BPM Events Admin utility ("Start" command). The server recovers its previous state from the database, and reprocesses the failing event.