Order Responses Stuck In SAF With OutOfMemoryError
(Doc ID 2226756.1)
Last updated on JANUARY 21, 2024
Applies to:
Oracle Communications ASAP - Version 7.2.0 and laterInformation in this document applies to any platform.
Symptoms
Orders are not completing in ASAP
The following error is seen in the ASAP WebLogic logs:
#### <
#### <
at weblogic.jms.saf.SAFAgentAdmin.activate(SAFAgentAdmin.java:189)
at weblogic.jms.saf.SAFAgentDeployer.activate(SAFAgentDeployer.java:114)
at weblogic.messaging.saf.internal.SAFServiceAdmin.activate(SAFServiceAdmin.java:102)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:472)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:101)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
Caused By: java.lang.OutOfMemoryError: mmap failed with ENOMEM or EAGAIN
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 |