JMS Memory Error after restarting the the Analytics Event Router (Doc ID 2271589.1)

Last updated on DECEMBER 16, 2019

Applies to:

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)'> <> <> <> <1494311167611> <BEA-040321> <JMSServer "JMSServer-OracleKnowledgeAnalytics" is resuming.>
####<May 9, 2017 2:26:07 AM EDT> <Info> <Messaging> <host> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1494311167644> <BEA-282003> <The messaging kernel JMSServer-OracleKnowledgeAnalytics will use up to 536,870,912 bytes of memory before paging begins.>
####<May 9, 2017 2:26:07 AM EDT> <Info> <Store> <host> <AnalyticsEventRouter_Server> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1494311167649> <BEA-280008> <Opening the persistent file store "JMSServer-OracleKnowledgeAnalytics" for recovery: directory=/opt/inquira/Oracle/Middleware/Oracle_Home/user_projects/domains/KB/servers/AnalyticsEventRouter_Server/tmp requestedWritePolicy="Non-Durable" fileLockingEnabled=true driver="wlfileio3".>

####<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)'> <> <> <> <1494311340534> <BEA-040123> <Failed to start JMS Server "JMSServer-OracleKnowledgeAnalytics" due to java.lang.OutOfMemoryError: Java heap space.
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)'> <> <> <> <1494311340541> <BEA-310006> <Critical subsystem JMSServer.JMSServer-OracleKnowledgeAnalytics has failed. Setting server state to FAILED.
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)'> <> <> <> <1494311340542> <BEA-141197> <The deployment of JMSServer-OracleKnowledgeAnalytics failed.
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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.