Autoforecast crashes JWP: U00045014 'java.lang.OutOfMemoryError: "GC overhead limit exceeded"' or CPU consumption is high
search cancel

Autoforecast crashes JWP: U00045014 'java.lang.OutOfMemoryError: "GC overhead limit exceeded"' or CPU consumption is high


Article ID: 252101


Updated On:


CA Automic One Automation CA Automic Workload Automation - Automation Engine


AutoForecast crashes JWP process and causes java to run out of memory.

Below errors can be seen in the JWP log and trace files 

U00045014 Exception 'java.lang.OutOfMemoryError: "GC overhead limit exceeded"' in 'java.util.Optional.of():108'.

----------------------- Stack Trace -----------------------
java.lang.OutOfMemoryError: GC overhead limit exceeded


or uses up CPU and shows:
----------------------- Stack Trace -----------------------
java.lang.OutOfMemoryError: Java heap space

Logging into non-0 client crashes JWP, creates .hprof file
Still able to log into client 0


Release: 12.3.9

               21.0.4 and below

Component: Automation Engine

Functional Area: Auto-Forecast


This happens when a Daylight Saving Time change date is included in the Auto-Forecast. For instance if you have a CET time zone configured and run the Auto-forecast which includes October 30th – The JWP goes into a loop and eventually dies out of memory.  Or if you have a EST time zone configured and run the Autoforecast to include November 6, the same will happen.



Do not use AUTOFORECAST, or set AUTO_FORECAST_DAYS to something less than the number of days until the DST switch in UC_CLIENT_SETTINGS  or do not include the upcoming October 30th for Europe or November 6th for Americas in the calculation of the auto forecast.  For example, if October 30 is 10 days away, use AUTO_FORECAST_DAYS of 9 or less.

You can use the Auto-forecast as usual with your n number of days period post October 30th (or November 6th) – Keep in mind that since this is a bug with the DST change – If you do not upgrade to a future fixed version this is likely to happen again during the March DST change.

You can also update the timezone used in the client prior to the daylight saving time switch to a later date (like the 4th Sunday in December).  Then a day or two before the daylight saving time switch, change it back to what it was originally and deactivate any scheduled auto-forecast


Update to a fix version listed below or a newer version if available.


Fix version:


Component(s): Automation.Engine 21.0.5 - Available 


Release notes: "Fixed an issue where autoforecasting a JSCH with a timezone would cause an endless loop on the day of change from summer- to wintertime."

Additional Information

AutoForecast information