Essbase 21c: 'oracle.epm.jagent.process.context.EssbaseProcessContextManager' Context Process Notifications In jagent.log
(Doc ID 3073915.1)
Last updated on FEBRUARY 27, 2025
Applies to:
Hyperion Essbase - Version 21.6.0.0.0 and laterEssbase for OCI Marketplace - Version 21.1.0.0.1 Marketplace and later
Information in this document applies to any platform.
Symptoms
jagent.log contains:
[<DATE><TIME>] [essbase_server1] [NOTIFICATION] [] [oracle.JAGENT] [TID] [userId: ] [<ECID>] [APP: ESSBASE] [partition-name: DOMAIN] [tenant-name: GLOBAL] [SRC_CLASS: oracle.epm.jagent.process.context.EssbaseProcessContextManager] [SRC_METHOD: startApplication] While starting the app <APP>, found a context for the application [<APP>] which was also using same server port [<NUMBER>]. As application <APP> already unloaded, cleaning up the context.
...
[<DATE><TIME>] [essbase_server1] [NOTIFICATION] [] [oracle.JAGENT] [<TID>] [userId:<ID>] [<ECID>] [APP: ESSBASE] [partition-name: DOMAIN] [tenant-name: GLOBAL] [SRC_CLASS: oracle.epm.jagent.core.application.ApplicationPOJO] [SRC_METHOD: startApplication] Application [<APP>] started with process id [<NUMBER>] and port [<NUMBER>].
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |