Docfactory Identifier Process Uses 100% CPU Because Of Non Thread Safe HashMap Usage
Last updated on FEBRUARY 16, 2018
Applies to:Oracle Documaker - Version 12.3 and later
Information in this document applies to any platform.
On : 12.3 version, Enterprise Edition
Under high-load on multi-core servers the Identifier, and Receiver could get into a race condition causing failures to burst a stacked job into transactions, or start to consume a lot of CPU time.
The issue can be reproduced at will with the following steps:
1. Submit stacked jobs in HotFolder through DWS.
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