ERROR StatusLogger Unrecognized format specifier

[fatah16x]

job ended with exit code = 0 but execution log show message "ERROR StatusLogger Unrecognized format specifier".

how to hide or solve that message?because it will make false negatif for me when log message there is ERROR word

Talend Real-time Big Data Platform, enterprise

Version: 8

[Greg_Taffer]

In Talend Version 8, the message ERROR StatusLogger Unrecognized format specifier is a known Log4j2 initialization error. 

It typically occurs because the Log4j2 plugin cache file (Log4j2Plugins.dat) is missing or overwritten when multiple JAR files are merged into a "fat JAR" during the build process. 

While the job itself succeeds (exit code 0), this message appears in the console/log before the job starts. You can solve or hide this message using the following methods: 
 

1. Solve via Project Settings (Recommended) 
 

This error often stems from Java compatibility settings.
 

• Deactivate Java 17 Compatibility: Go to File > Edit Project Properties, then navigate to Build > Java Version. Uncheck the Enable Java 17 compatibility option, then rebuild and redeploy your job.
• Verify Java Environment: Ensure your Talend Studio and execution environment (Remote Engine) are both using the same supported Java version (typically Java 17 for Talend 8). 

2. Hide via JVM Parameters 
 

If you cannot change the project build, you can suppress these internal Log4j2 status messages by forcing a simpler logger factory that doesn't trigger the error:
 

• Add JVM Argument: Add the following parameter to your job's execution or the Talend Runtime/JobServer configuration:
  -Dlog4j2.loggerContextFactory=org.apache.logging.log4j.simple.SimpleLoggerContextFactory
• Ignore Thread Context: For newer Log4j2 versions, you may also need:
  -Dlog4j.ignoreTCL=true 

3. Modify Log4j2 Configuration
 

You can attempt to silence the StatusLogger directly in the configuration:
 

• Edit Log4j Template: Open File > Edit Project Properties > Log4j. In the XML template, ensure the root <Configuration> tag has the attribute status="OFF" or status="FATAL".
• Filter Specific Strings: If the message persists in the execution log, you can use a Log4j2 RegexFilter in your appender to drop any log line containing the string "Unrecognized format specifier". 

4. Patching (Enterprise Only)

As an Enterprise user, check for the latest cumulative monthly patches (e.g., R2025-09v2 or later) on the Talend Update Portal. These patches often include fixes for Log4j2 library conflicts introduced in earlier v8 releases.

[fatah16x]

thank you for your response and reply.

I tried to follow the methods that you given but not impact (solve)

- start from change project settings > java setting to java 8 because our environment using java 17.

- add JVM parameter -Dlog4j2.loggerContextFactory=org.apache.logging.log4j.simple.SimpleLoggerContextFactory and -Dlog4j.ignoreTCL=true

- modify log4j2 with add status="OFF" in configuration tag

- and last that i don't want do to update version but i commit to follow you. i update version studio to R2026-03

all the methods I have done but not hide or solve case.

FYI, my friends give an underrate and underestimates to TALEND because the solution for errors and flexibility of use. But I still trust to TALEND give me the best answer, however long and complex.

we use enterprise product with 6 users license. 

[Greg_Taffer]

What patch are you currently running?

[fatah16x]

R2026-03

[Greg_Taffer]

Thanks! At this point, I would recommend opening a Support Case for our Support Team.

[fatah16x]

so what we can do now?is that name as an support for enterprise user?