Local optimization not considering lazy loading during startup - "unknown mode for composite" and "Cached NULL_INVOCATION_CONTEXT for address"
(Doc ID 2815464.1)
Last updated on OCTOBER 22, 2021
Applies to:Oracle SOA Suite - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Fabric
Local Optimization not taking in account lazy loading during initialization
We are observing some issues with use of local optimization that mainly happens during startup/ initialization. Customer as some composite that will call other composite for each local optimization is expected to be used.
In order to diagnose local optimization problems loggers "oracle.integration.platform.blocks.local" and "oracle.integration.platform.blocks.soap" where set to "TRACE:1"
The test case with customer processes consists in having some load test running and restart one the managed servers. In the managed server that is starting we verify that for invocations that where expected to be using local optimization but are not we have a message in the diagnostic logs with "unknown mode for composite: ":
... [TRACE]  [oracle.integration.platform.blocks.local] ... [J2EE_APP.name: soa-infra] ... [WEBSERVICE.name: baseHandlerService] ... [SRC_CLASS: oracle.integration.platform.blocks.local.LocalInvocationProcessor] [SRC_METHOD: getLocalInvocationInfo] unknown mode for composite: ....
From my research this "unknown mode" seems to happen because the component that is being called is not yet deployed and could not check if component is active; as such it is "marked" as not being eligible to be called locally; this information is cached and subsequent calls will not use local optimization. We see message in the logs with "Cached NULL_INVOCATION_CONTEXT for address":
... [TRACE]  [oracle.integration.platform.blocks.local] ... [J2EE_APP.name: soa-infra] ... [WEBSERVICE.name: baseHandlerService] ... [SRC_CLASS: oracle.integration.platform.blocks.local.LocalInvocationProcessor] [SRC_METHOD: getLocalInvocationInfo] Cached NULL_INVOCATION_CONTEXT for address ...
Is lazy loading is taken in account to check if composite is active? What is the cause for the TRACE message in logs with "unknown mode for composite: " ?
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