[Java SE] JNDI Providers: LDAP, DNS, RMI, or CORBA Raise "java.lang.IllegalArgumentException" or "javax.naming.NamingException" After Updating to the April 2022 CPU
(Doc ID 2864926.1)
Last updated on APRIL 29, 2022
Applies to:Java SE JDK and JRE - Version 7 and later
Information in this document applies to any platform.
This document applies to any of the April 2022 Critical Patch Update (CPU) Java SE releases:
- JDK 18.0.1
- JDK 17.0.3
- JDK 11.0.15
- JDK 8 Update 331
- JDK 7 Update 341
This document does not apply to JDKs released prior to the April 2022 CPU:
- JDK 18 GA (initial release)
- JDK 17.0.2 or older
- JDK 11.0.14 or older
- JDK 8 Update 321 or older
- JDK 7 Update 331 or older
After updating to one of the April 2022 CPU JDK releases, such as JDK 8 Update 331 (8u331), you may notice applications that build Uniform Resource Locator (URL) or Uniform Resource Identifier (URI) strings in a JNDI context may fail with a java.lang.IllegalArgumentException or javax.naming.NamingException (or a subclass of it). Reverting to a previous JDK update, such as JDK 8u321, allows the applications to work again.
The following JDK 8u331 exception stack trace has been reported in several WebLogic Server (WLS) instances:
The key change to trigger this issue is an update to one of the April 2022 CPU JDK releases, such as JDK 8u331.
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