Known Issues for WebLogic Management

When an API that returns a 409 - Conflict error message for validation, for example, when installing the latest patches:

  "data": {
    "code": "Conflict",
    "message": "Patch readiness status must be OK for domain <domain-ocid>
Current status is ERROR"
  },
  "status": "409 Conflict"

Rerunning the operation results in a different error:

"data": {
    "code": "Conflict",
    "message": "Resource <domain-ocid> is currently being modified."
  }
  "status": "409 Conflict"

Wait 15 to 30 seconds before making the second call to the API.

When you restart a domain, the server states should change from Stopping to Restarting to Running. However, WebLogic Management plugin does not report intermediate server states. This means the server state displays Running throughout the restart operation.

Monitor the server status in the work request for the domain restart operation.

If the Use scripts to start and stop servers option is selected in the Domain Settings , when you try to apply the latest patches WebLogic Management tries to use Node Manager for the stop and start operations.

This issue is harmless. However, if you have removed the Node Manager files, patching fails. You can restore patching functionality by restoring the Node Manager files you deleted.

On a managed instance, if a domain is sharing the middleware with another domain and you apply patches to one of the domains, the servers in both the domains are restarted after the middleware is patched. However, the domain that was not patched shows a Needs Attention state. This happens because Node Manager is not started for the domain, so WebLogic Management cannot get the state of domain's servers.

Start Node Manager on the managed instance and scan to update servers and domain states.

If a domain has no listen address for its servers and those servers are spread across nodes, when you scan one node (managed instance) the servers are associated with the correct managed instance when viewing the domain. However, the servers on the other nodes are erased and the managed instances are no longer associated).

We recommend you configure a listen address in domains to avoid this issue.

When WebLogic Management applies patches it rolls back any patches that are known to conflict with the patches being applied. On rare occasions OPatch removes the patch backup contents from MW_HOME/.patch_storage before fully removing the patch. This results in an error and is displayed in the Work Request messages, for example:

Request for managed instance with ID ocid1.instance.oc1.iad.<instance-ocid> failed.

Response of request: [ Failed to rollback conflicting patches on middleware MW_HOME for domain DOMAIN_NAME.
Error is Failed to rollback patch [patch-id-number] with error UtilSession failed: Prerequisite check "CheckRollbackable" failed.. ].

To recover, do one of the following:

• Contact Support with this error message to obtain the contents to be replaced.
• Get the missing patch contents from another middleware: MW_HOME/.patch_storage/<patch id>_<date>.
• Install middleware on another instance, apply the patch, and get the contents of MW_HOME/.patch_storage/<patch id>_<date>.

After you have the contents from .patch_storage, move the contents into the MW_HOME/.patch_storage on the instance on which the failure occurred. Then, do one of the following:

• Run Apply Latest Patches again.
• Stop all servers and roll back the patch using MW_HOME/OPatch nrollback -id <patch id>.

If you have a WebLogic Server domain without boot.properties and you have set the domain to use OCI secrets for WebLogic or Node Manager, the credentials of the secret OCIDs are sent with scan, patch, and other lifecycle operations (start, stop, restart, or rollback).

After a lifecycle operation is completed, the service automatically runs a scan operation to get the correct state of all servers, but does not send the credentials of the secret OCIDs. Rather, the scan operation reverts to using domain credentials. If the domain credentials are not accessible, scan results are incorrect.