Order and Service Management (Communications Industry) (MOSC)

MOSC Banner

Why does OSM take so long to Initialize Orchestration?

edited Oct 15, 2016 5:17AM in Order and Service Management (Communications Industry) (MOSC) 6 commentsAnswered ✓

Any time we do a cache refresh or system restart we come across these messages in our logs

"

[ INFO] - 2016-09-27 16:20:35 c:? - Initializing orchestration model - COMPLETED

[ INFO] - 2016-09-27 16:20:37 c:? - Initializing orchestration model - COMPLETED

[ INFO] - 2016-09-27 16:20:45 c:? - Initializing orchestration model - COMPLETED

[ INFO] - 2016-09-27 16:20:58 c:? - Initializing orchestration model - COMPLETED

........

........

........

[ INFO] - 2016-09-27 16:30:42 c:? - Initializing orchestration model - COMPLETED

[ INFO] - 2016-09-27 16:30:51 c:? - Initializing orchestration model - COMPLETED

[ INFO] - 2016-09-27 16:31:02 c:? - Initializing orchestration model - COMPLETED

"

This process typically lasts 10+ minutes and tends to corrupt the first order that comes in. Is there something we can do to improve the efficiency of this initialization? Or at least have it occur before it attempts to process orders?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center