Skip to main content
Announcements
Qlik Connect 2025! Join us in Orlando join us for 3 days of immersive learning: REGISTER TODAY

Qlik Talend Product: module java.base does not opens java.util to unnamed module

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Uma_Ganesh
Support

Qlik Talend Product: module java.base does not opens java.util to unnamed module

Last Update:

Feb 25, 2025 9:07:13 PM

Updated By:

Xiaodi_Shi

Created date:

Feb 25, 2025 9:07:13 PM

You may be getting the following error while running a Talend Bigdata Job:


java.lang.reflect.InaccessibleObjectException: Unable to make field private final java.util.Map java.util.Collections$UnmodifiableMap.m accessible: module java.base does not "opens java.util" to unnamed module @39ebfb56>

 

Resolution

To resolve the issue while maintaining JDK 17 support, the following steps are performed:

For a single Spark job:

  1. Navigate to Spark job -> Advanced Settings -> Use specific JVM Args.
  2. Add the following line:
    --add-opens=java.base/java.util=ALL-UNNAMED

For all Jobs:

  1. Go to Window -> Preferences -> Talend -> Run/Debug.
  2. Add the following JVM argument:
    --add-opens=java.base/java.util=ALL-UNNAMED

After adding this JVM argument line to the Job configurations, the issue was resolved.

 

Cause

The issue occurred because you was using JDK 17 and Talend 8.0.1. As JDK 17 introduced stricter module access controls, which led to this error when accessing certain parts of the java.util package. 

 

Related Content

For more information about Java 17 Migration, please refer to this official article

Qlik-Talend-Products-Java-17-Migration-Guide

 

Environment

Labels (2)