Resolving Component Dependency Using Order Scope Causes Server To Throw an Out Of Memory Error Or Crash
Last updated on AUGUST 15, 2016
Applies to:Oracle Communications Order and Service Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.0 to 7.3.1]
Information in this document applies to any platform.
Customer uses order scope update to update milestones in the order template using a query task. On one particular milestone update, the dependency between two components gets resolved. At this point when processing this milestone in a large order, the servers became very slow. On processing the same milestones (for remaining bundles in the order) the server throws either an out of memory exception or crashes.
Order scope update or the OSM internal code to resolve the dependency is putting a load on the server.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms