My Oracle Support Banner

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 4.3.0.5.0 to 4.4.0.0.0 [Release 4.3 to 4.4]
Oracle Utilities Customer Care and Billing - Version 2.7.0.1.0 to 2.7.0.3.0 [Release 2.7]
Oracle Utilities Customer to Meter Base - Version 2.7.0.1.0 to 2.7.0.3.0 [Release 2.7]
Information in this document applies to any platform.

Symptoms

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.

Changes

 

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
Changes
Cause
Solution
References

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