Groovy Class Loader Initialization Causing Long Delays or Timeouts
(Doc ID 2736745.1)
Last updated on DECEMBER 14, 2020
Applies to:Oracle Utilities Framework - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 4.3 to 4.4]
Oracle Utilities Customer Care and Billing - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 2.7]
Oracle Utilities Customer to Meter Base - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 2.7]
Information in this document applies to any platform.
The first execution of an IWS Service which executes a Groovy script after a system reboot incurs a couple of performance penalties both related to groovy.
1. Because any service script can possibly contain a groovy step, groovy class loaders are initialized taking more than 10 seconds in some scenarios
2. If a script actually contains groovy members the initial groovy compile requires even more compiler configuration
These delays cause upstream transactions to timeout, and locks can be seen in java stack traces in the groovy compilation tasks.
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