Hello Community,

I am encountering an issue while creating a new WebLogic domain after applying the following patch:

Product: Oracle WebLogic Server

During domain creation, the script fails at the readTemplate() step with the following error:

"BUILD FAILED
Picked up _JAVA_OPTIONS: -Djava.security.egd=file:/dev/./urandom

Initializing WebLogic Scripting Tool (WLST) ...

Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Error: readTemplate() failed. Do dumpStack() to see details.
Error: runCmd() failed. Do dumpStack() to see details.
Traceback (most recent call last):
File "/home/psadm2/psadm2_wlsdomain.py", line 56, in <module>
readTemplate(templatejar)
File "/tmp/WLSTOfflineIni14760566261646255841.py", line 21, in readTemplate
command("readTemplate", templateFileName, topologyProfile, suppressTargeting)
File "/tmp/WLSTOfflineIni14760566261646255841.py", line 19, in command
return WLS.runCmd(name, args)

    at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)

    at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:3124)

    at com.oracle.cie.domain.script.jython.WLScriptContext.runCmd(WLScriptContext.java:738)

    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)

com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.aspect.ConfigParsingException: java.lang.reflect.InvocationTargetException: security.xml

Problem invoking WLST - Traceback (most recent call last):
File "/home/psadm2/psadm2_wlsdomain.py", line 56, in <module>
readTemplate(templatejar)
File "/tmp/WLSTOfflineIni14760566261646255841.py", line 21, in readTemplate
command("readTemplate", templateFileName, topologyProfile, suppressTargeting)
File "/tmp/WLSTOfflineIni14760566261646255841.py", line 19, in command
return WLS.runCmd(name, args)

    at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)

    at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:3124)

    at com.oracle.cie.domain.script.jython.WLScriptContext.runCmd(WLScriptContext.java:738)

    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)

com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.aspect.ConfigParsingException: java.lang.reflect.InvocationTargetException: security.xml

PIA_INSTALL_FAILED"

Key Observation:

• When Patch 39164443 is applied, domain creation fails consistently with the above error.
• When the patch is rolled back, using the same WLST script, same JDK, and same templates, the domain creation works fine.

This strongly suggests the issue is introduced by Patch 39164443.

Questions to the Community:

• Has anyone else faced WLST domain creation failures involving security.xml after applying the April 2026 CPU?
• Can someone confirm whether this is a known bug with this PSU?
• Are there any workarounds, post‑patch steps, or MOS notes (for example related to domain templates, JDK compatibility, or security configuration)?
• Has anyone successfully created a new domain after this patch, and if so, were any special steps required?

Any insights or confirmation would be greatly appreciated.

Thanks in advance.

It's not just you. I get the same thing after applying either the 39168284 or 39164443 patch to Q1 weblogic (251223). I have a ticket open, but no resolution yet.