IPM Migration Service is Causing the Information Broker to Hang
(Doc ID 2667016.1)
Last updated on MAY 07, 2020
Applies to:Oracle Imaging and Process Management - Version 10.1.3.6 and later
Information in this document applies to any platform.
When running the IPM Migration service, the Information Broker tool will stop functioning properly. Initially, there are errors in the log, but then it will crash the IPM Architecture on the server where Information Broker is located. When the architecture crashes, sometimes Windows Services shows as stopped, and sometimes it still shows as running. When attempting to stop the service, it will fail because it is actually running.
The amount of time it takes for the migration service to cause this appears to be linked to the quantity of files it has retrieved. It happens slower when less worker threads are used and faster when there are more, but it always appears to happen.
This does not relate to specific documents or document types. Documents are able to be migrated during the "Reset Failures".
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document