Java SE 8 Update 201+ Web Start Crashes with "StackOverflowError" when Accessing Cached URL
(Doc ID 2527608.1)
Last updated on NOVEMBER 14, 2020
Applies to:Java SE JDK and JRE - Version 8 to 8
Oracle Forms - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Java SE 8 Update 201+ Web Start crashes with "StackOverflowError" when accessing a cached URL.
After clearing the Java cache, accessing the URL is again successful. However, when trying to run the URL again, the "Java..." splash page for Java Web Start is displayed, but after 10-15 seconds, the splash screen closes and nothing else happens. Monitoring this startup attempt with Task Manager shows: when the URL is initiated, the 'javaws.exe' is running; when the splash page closes, the 'javaws.exe' process also closes.
The issue is particular to Java Web Start and does not occur with Java Plugin.
Java Web Start trace output:
This issue is known to occur with Oracle Forms clients that use Java Web Start, when Forms is configured with OAM/Webgate. OAM/Webgate enables SSO for Forms through parameter ssoMode=webgate in the formsweb.cfg configuration file. See -> How to Integrate Forms 12c with OAM after a 12c Forms/Reports Installation (Doc ID 2096585.1). However, even when 'ssoMode=false' is set in the formsweb.cfg configuration file, the OAM/Webgate configuration still affects Forms when the Java WebStart is used to call a form. However, no issue occurs if:
- OAM/Webgate is disabled by commenting out the line "include webgate.conf" in the "httpd.conf" configuration file.
- Java Plugin with a Forms Client applet (the default method of accessing forms) is used.
Updating to Java SE 8 Update 201 or 202 can trigger the issue for some Java Web Start applications.
Converting from Java Plugin to Java Web Start when using Java SE 8 Update 201 or 202 can also trigger the issue.
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