JMS Memory Error after restarting the the Analytics Event Router
(Doc ID 2271589.1)
Last updated on DECEMBER 16, 2019
Applies to:
Oracle Knowledge - Version 8.6 and laterInformation in this document applies to any platform.
Symptoms
JMS event router will not start after applying the patch. The JMS queue continued to recieve data while the patch was being applied. The data in the queue was much larger when trying to restart it. this requires that more memory be given to the JMS queue.
Changes
####<May 9, 2017 2:26:07 AM EDT> <Info> <JMS> <host> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <
####<May 9, 2017 2:26:07 AM EDT> <Info> <Messaging> <host> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <
####<May 9, 2017 2:26:07 AM EDT> <Info> <Store> <host> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <
####<May 9, 2017 2:29:00 AM EDT> <Error> <JMS> <lxindinqprd01.KB.com> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <
java.lang.OutOfMemoryError: Java heap space
at java.util.HashMap.resize(HashMap.java:580)
at java.util.HashMap.addEntry(HashMap.java:879)
####<May 9, 2017 2:29:00 AM EDT> <Critical> <Health> <host> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <
Reason: weblogic.management.DeploymentException: Internal error activating the JMS Server JMSServer-OracleKnowledgeAnalytics: java.lang.OutOfMemoryError: Java heap space>
####<May 9, 2017 2:29:00 AM EDT> <Warning> <Management> <host> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <
weblogic.management.DeploymentException: Internal error activating the JMS Server JMSServer-OracleKnowledgeAnalytics: java.lang.OutOfMemoryError: Java heap space
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:234)
at weblogic.management.utils.GenericManagedDeployment.activate(GenericManagedDeployment.java:158)
at weblogic.management.utils.GenericDeploymentManager.activate(GenericDeploymentManager.java:184)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:211)
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 |
Changes |
Cause |
Solution |