E-WL: E-PN: WebLogic Memory Increasing Excessively if Push Notification is Enabled (Doc ID 2991921.1)

Last updated on MAY 14, 2024

Applies to:

Symptoms

Customers are using Push Notification and noticing that WebLogic is consuming a lot of memory which exceeds way above the heap size. To investigate further, we captured a memory dump as follows:

/*********************************************************************************************/

1. Run the following command

<JAVA_HOME>\bin\jcmd <pid> Thread.print > jcmdnew.log

where <pid> is the PID of the PIA Java process.

2. Upload the jcmdnew.log to the service request.

3. Run the command below from an admin command prompt:
tasklist /v txt > tasksnew.txt

4. Upload the tasksnew.txt file to the service request.

/**********************************************************************************************/

Looking at the generated tasksnew.txt file, we see the following error, over and over:

/**********************************************************************************************/

"AsyncHandler" #1519 daemon prio=2 os_prio=-2 cpu=1000.00ms elapsed=14066.49s tid=0x000000003c346000 nid=0x7b4c waiting for monitor entry  [0x00000000586bf000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at com.peoplesoft.pt.events.PublishEventService.execute(PublishEventService.java:116)
    - waiting to lock <0x00000007086c4578> (a java.lang.Class for com.peoplesoft.pt.events.PublishEventService)
    at com.peoplesoft.pt.events.EventDelegate.publishToReplicatorServer(EventDelegate.java:184)
    at com.peoplesoft.pt.events.JoltSessionWrapper.onReply(JoltSessionWrapper.java:256)
    at bea.jolt.EventDispatcher.run(JoltSession.java:997)

......etc

"AsyncHandler" #1521 daemon prio=2 os_prio=-2 cpu=1000.00ms elapsed=14066.48s tid=0x000000003c347000 nid=0x602c waiting for monitor entry  [0x000000005873f000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at com.peoplesoft.pt.events.PublishEventService.execute(PublishEventService.java:116)
    - waiting to lock <0x00000007086c4578> (a java.lang.Class for com.peoplesoft.pt.events.PublishEventService)
    at com.peoplesoft.pt.events.EventDelegate.publishToReplicatorServer(EventDelegate.java:184)
    at com.peoplesoft.pt.events.JoltSessionWrapper.onReply(JoltSessionWrapper.java:256)
    at bea.jolt.EventDispatcher.run(JoltSession.java:997)

..... etc

/**********************************************************************************************/

Cause

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