The following sections describe known limitations for WebLogic Deploy Tooling. Each issue may contain a workaround or an associated issue number.
ISSUE: Deploy a WebLogic Kubernetes Operator domain with Model-in-Image (MII) produces introspector failures.
ACTION: WDT 4.0 made significant changes to archive file path handling that required changes in WebLogic Kubernetes Operator, which became available starting in WebLogic Kubernetes Operator 4.2.0. Upgrade to WebLogic Kubernetes Operator 4.2.0+ to resolve the issue.
SEVERE messagesISSUE:
The discoverDomain STDOUT contains many SEVERE messages about cd() and ls() when it is run against a 12.2.1.0
domain. The Discover Domain Tool navigates through the domain MBeans using WLST to determine which MBeans are present
in a domain. When it tests an MBean that is not present, an error message is logged by WLST. There is no 12.2.1.0 PSU
available to address this WLST problem. It is resolved in 12.2.1.1.
ACTION: Ignore the following messages logged during discovery of a 12.2.1.0 domain.
<Jan 14, 2019 1:14:21 PM> <SEVERE> <CommandExceptionHandler> <handleException> <> <Error: cd() failed.>
<Jan 14, 2019 1:14:21 PM> <SEVERE> <CommandExceptionHandler> <handleException> <> <Error: ls() failed.>
ISSUE: The Create Domain Tool cannot initialize RCU for 11g JRF domains. The tool will issue error messages in the log and terminate the create process.
ACTION:
Run the WLS rcu command before executing createDomain for JRF domains
ISSUE: For WLS versions prior to 14.1.1, there is a problem setting the CredentialEncrypted attribute in the
topology/SecurityConfiguration folder. The value is not encrypted properly in the configuration and the domain will
fail to start with the error:
java.lang.IllegalArgumentException: In production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean
ACTION: Contact Oracle Support to obtain the patch for bug number 30874677 for your WebLogic Server version before running the tool.
RotateLogOnStartup attributeISSUE: For existing WLS versions, there is a problem setting the RotateLogOnStartup attribute in various log file
folders. The value is not persisted correctly, and the assignment will not be present when the domain is started.
ACTION: Contact Oracle Support to obtain the patch for bug number 29547985 for your WebLogic Server version before running the tool.
ISSUE: Discovering a domain does not attempt to discover users and groups defined in any configured Authentication Provider type.
ACTION: This should only be an issue for the domains using the DefaultAuthenticator, which uses the Embedded LDAP
server that runs inside WebLogic Server as its user and group store. To discover the users and groups in the
DefaultAuthenticator, use the -discover_security_provider_data switch with an argument that includes the
DefaultAuthenticator (e.g., ALL or a comma-separated list of provider types like DefaultAuthenticator,DefaultCredentialMapper).
ISSUE: After a JRF domain is created, the jps-config.xml and jps-config-jse.xml files contain clear text password for the key store.
ACTION: You will need to create a key store using Oracle Wallet and change the key store provider priority in the
JVM. See Oracle Support Doc ID 2215283.1 for details. If you are creating a JRF domain using Oracle Autonomous
Transaction Database, you can use the SSO key stores instead of JKS key stores, the generated jps-config.xml and
jps-config-jse.xml files will then use the SSO key stores without any clear text password.
domainInfo:
RCUDbInfo:
databaseType : ATP
rcu_prefix : FMW
rcu_schema_password : '...'
rcu_admin_password: '...'
rcu_db_user : admin
tns.alias : myatp_tp
javax.net.ssl.keyStoreType: SSO
javax.net.ssl.trustStoreType: SSO
ISSUE: WDT Create Domain does not appear to support SSH.
ACTION: WDT Create Domain does not support SSH cause domain creation needs to run on the machine where the domain will exist to ensure that paths in the generated domain files point to the actual Java and Oracle Homes. To support Create Domain via SSH, WDT would need to install itself on the remote machine and then execute its commands there. The workaround is for the user to temporarily install WDT, create the domain, and uninstall WDT.
ISSUE: WDT does not correctly handle the @@JAVA_HOME@@, @@PWD@@, and @@TMP path tokens.
ACTION: Do not use these path tokens in an SSH context because WDT does not currently provide a way for the user to supply “remote” values for these paths.
ISSUE: WDT Update Domain does not properly deploy a new version of an application to support non-disruptive updates.
ACTION: While we fully intend to resolve this issue in an upcoming release, the workaround for now is to use the
weblogic.Deployer tool to redeploy the application pointing at the new source files, as described in the
WebLogic Server documentation.
ISSUE: WDT Update Domain may fail if trying to update the values of RemoteAnonymousRmiiiopEnabled and
RemoteAnonymousRmit3Enabled in the same Update Domain call.
####<Jan 6, 2025 12:38:06 PM> <SEVERE> <update> <main> <WLSDPLY-09015> <updateDomain deployment failed: activate() failed: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException>
Issue Log for updateDomain version 4.3.0 running WebLogic version 12.2.1.4.0.240704 in online mode against server using WebLogic version 12.2.1.4.0.240704:
WARNING Messages:
1. WLSDPLY-09012: While handling an error, failed to stop the current edit session and disconnect: undo() failed: None
SEVERE Messages:
1. WLSDPLY-09015: updateDomain deployment failed: activate() failed: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
Total: SEVERE : 1 WARNING : 1
updateDomain.sh failed (exit code = 2)
ACTION: This is caused by WebLogic Server Bug 37443991. To resolve this issue, please file an SR with Oracle Support and ask for a patch for Bug 37443991. The only known workarounds are to either split these two updates into separate online Update Domain calls or use offline Update Domain.