E1: JAS: High CPU Utilization in HTML Server with Reference to 'at com.jdedwards.jas.ExpiredPasswordNotificationExecutor.getExpiryUsers' in Thread Dumps
(Doc ID 3065712.1)
Last updated on FEBRUARY 16, 2025
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
The java process associated HTML server consumes high CPU utilization on the server which is resolved only when restarting the HTML instance. The issue reappears few days after restart.
When thread dumps are captured to check for the process consuming the most CPU the following call stack referencing Password Notification service is seen.
java.lang.Thread.State: RUNNABLE
at java.lang.String.toUpperCase(String.java:2833)
at com.jdedwards.database.base.JDBField.initializeConstructor(Unknown Source)
at com.jdedwards.database.base.JDBField.initializeConstructor(Unknown Source)
at com.jdedwards.database.base.JDBField.<init>(Unknown Source)
at com.jdedwards.database.base.JDBField.<init>(Unknown Source)
at com.jdedwards.database.base.JDBField.newField(Unknown Source)
at com.jdedwards.database.impl.transform.JDBTransformFieldMap.getString(Unknown Source)
at com.jdedwards.database.impl.resultset.JDBFieldMapDelegate.getString(Unknown Source)
at com.jdedwards.jas.ExpiredPasswordNotificationExecutor.getExpiryUsers(Unknown Source)
at com.jdedwards.jas.ExpiredPasswordNotificationExecutor.execute(Unknown Source)
at com.jdedwards.jas.ExpiredPasswordNotificationExecutor$1.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
at java.lang.String.toUpperCase(String.java:2833)
at com.jdedwards.database.base.JDBField.initializeConstructor(Unknown Source)
at com.jdedwards.database.base.JDBField.initializeConstructor(Unknown Source)
at com.jdedwards.database.base.JDBField.<init>(Unknown Source)
at com.jdedwards.database.base.JDBField.<init>(Unknown Source)
at com.jdedwards.database.base.JDBField.newField(Unknown Source)
at com.jdedwards.database.impl.transform.JDBTransformFieldMap.getString(Unknown Source)
at com.jdedwards.database.impl.resultset.JDBFieldMapDelegate.getString(Unknown Source)
at com.jdedwards.jas.ExpiredPasswordNotificationExecutor.getExpiryUsers(Unknown Source)
at com.jdedwards.jas.ExpiredPasswordNotificationExecutor.execute(Unknown Source)
at com.jdedwards.jas.ExpiredPasswordNotificationExecutor$1.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
Steps
- Check CPU utilization on the HTML instance
- Capture thread dumps following procedure in Unexpected High CPU Usage with WebLogic Server (WLS) Support Pattern (Doc ID 779349.1)
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 |