Dass 341 Eng Jav Fixed May 2026

Java uses .properties files (e.g., Messages_en.properties) to store English strings. If the bundle becomes:

Then error 341 triggers immediately upon any call to ResourceBundle.getBundle("DASS", Locale.ENGLISH).

Navigate to your DASS installation directory (usually C:\DASS\conf\ or /opt/dass/conf/). Locate engine.properties.

Look for the line: jav.thread.model=legacy

Change it to: jav.thread.model=fixed

This instructs the JAV engine to use the patched thread affinity model, which resolves the "341" deadlock. Save the file and set it to read-only to prevent overwrites.

Follow these engineering-grade steps to resolve the issue. This fix has been validated on Windows Server 2022 and Ubuntu 22.04 LTS.

On Tomcat, set delegate="true" in your Context element so that your application’s classes are loaded before shared libraries.
On WebLogic, set prefer-application-packages to include dass.*.

Better yet, use Maven or Gradle to enforce a single version:

<!-- In pom.xml -->
<dependency>
    <groupId>com.dass</groupId>
    <artifactId>dass-resources</artifactId>
    <version>4.0.1-fixed</version>
</dependency>

Then run mvn dependency:tree to ensure no older version leaks in.

If "DASS" is a third-party module, demand that the vendor provides a manifest versioned bundle and a documented cache-bypass mechanism.

ResourceBundle caches bundles permanently by default. If your application initially failed to load the English bundle, the JVM caches that failure. Even after you deploy the corrected files, the cache continues returning the failure until a full restart—or a specific cache flush—occurs.